tursodatabase / tursodatabase/libsql
About the undocumented SQLD_HEARTBEAT_URL
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
First of all thank you for Libsql! It's been very fun to mess around with and I'm hoping to make it central to my own stack.
I started experimenting with the Docker image and noticed the logs kept mentioning something about an undefined heartbeat url. After some digging in the codebase I discovered the ENV SQLD_HEARTBEAT_URL.
I tried to set it and while libsql-server does seem to find it:
2025-01-12T21:34:56.201098Z INFO libsql_server: Server sending heartbeat to URL https://11895tjht5.execute-api.eu-west-1.amazonaws.com/prod every 30s
I'm not seeing any hits on my endpoint.
Did I try to implement an unfinished feature or is this a legitimate bug?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Docker image and the libsql-server handling of SQLD_HEARTBEAT_URL. Trace how the configured URL is used and verify whether requests reach the endpoint. Done means either documenting the supported heartbeat configuration and behavior or recording the confirmed bug and its required fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- databases, devops
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100