Allow endpoint configuration through the Cachet API
See original GitHub issueWith the Cachet API, we can retrieve the list of configured components at /api/v1/components
, then perform a basic health check for all components with an URL through GET.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Enabling API caching to enhance responsiveness
You can enable API caching in Amazon API Gateway to cache your endpoint's responses. With caching, you can reduce the number of calls...
Read more >Advanced API Usage - Cachet Documentation
You can perform basic searches on many of the endpoints, by passing through a key/value pair containing the column name and the value...
Read more >Implementing API cache control | Fastly Help Guides
This guide explains how to implement API cache control. Once you've enabled API caching, and ensured purging works properly with your cached ...
Read more >Add caching to improve performance in Azure API Management
Add the caching policies · Browse to your APIM instance. · Select the API tab. · Click Demo Conference API from your API...
Read more >Configure InfluxDB OSS - InfluxData Documentation
InfluxDB first checks for the -config option and then for the environment variable. Configuration settings. Note: To set or override settings in a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m currently trying to wrap up the work on supporting multiple URLs, before tackling this issue. This one may be a bigger revamp, so I wanna make sure 0.3 is done and working. I’m not happy with my current approach on it, thus I’m taking longer to get it done.
Don’t worry, this issue is not forgotten and it is on the top of my list to get done. It is a great idea and I really wanna get it implemented. Kudos to @xel1045 for the suggestion.
I gotta say, that’s a good idea. I would make this as an optional way of setting it up as not always we want to have the same check for every single component. Say you wanna monitor a page and check if the body contains an specific string, but this string is not present in the other components.
For the status code range, I’ll create a separate issue for it.
Nonetheless, I will address those two things on milestone 0.4. I want to get 0.3 out of the door soon and your suggestions will take a little longer to get done.
Thanks for all these suggestion, they are great ideas!