-
-
Notifications
You must be signed in to change notification settings - Fork 810
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
custom name instead of automatically generated UUID #491
Comments
I like this idea and wish I had thought of it from the start. There has also been interest in additional authentication for the ping endpoints. Let's say there was a per-project "ping key". The ping URLs could look something like:
Let's say I have a web application that runs 10 periodic processes I want to monitor. Currently, with UUIDs, I have 10 different ping URLs. I must treat each ping URL as a secret – the same way I would be treating database credentials, SMTP credentials etc. The UUIDs are not human-readable – it is easy to mistake one ping URL for another. Now, with a "ping key" and custom names, I would only need to treat the ping key as a secret. It would be easy to construct all 10 ping URLs from just the key and the custom names (which don't need to be secret).
No
I think yes, but it would take a fair bit of work. I think I could hack something together relatively quickly, but the main effort would go into
|
Is this issue in a roadmap? It would be great feature to have |
There isn't really a roadmap but yes, I do plan to work on this feature. I'm taking a closer look at it now and putting together a plan (all subject to change).
On the last point: let's say the project has two checks with the name "Database Backup". What should happen when a client pings "database-backup"? We have a few choices:
I think the first option is the correct choice – I think errors and failures should be loud and explicit. If you want to ping a check by its name, then the name has to be unique within the project. If you use non-unique slug anyway, neither check registers a ping, which eventually triggers notifications, and you can then investigate. Comments, ideas, suggestions welcome! |
An initial version is ready and deployed to https://healthchecks.io. In the checks table, "Ping URL" column, there is now a uuid/slug switcher: You can generate the ping key in project's Settings page: HTTP status codes when using {ping_key}/{slug} URLs:
Healthchecks.io also does rate-limiting at nginx level:
The documentation is not yet updated with the new URL format – I wanted to get this early version out so you can try it out :-) |
thank you, an awesome feature !!! works fine |
Could we get a possibility to use a custom name in URL instead of randomly generated UUID?
So instead of url being something like
healthchecks.example.com/ping/543dc814-81a5-11eb-8dcd-0242ac130003
I would like to be able to set it to something like
healthchecks.example.com/ping/name-of-my-service
For example I would then be able to specify the URL in docker-compose like this:
and would not have to first create the endpoint in healthchecks and then update the url to docker-compose.
Is this possible to achieve currently? and if not is this something that is feasible to implement?
The text was updated successfully, but these errors were encountered: