Skip to content
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

Feature Request: client health update #95

Closed
kensel opened this issue Mar 11, 2021 · 4 comments · Fixed by #724
Closed

Feature Request: client health update #95

kensel opened this issue Mar 11, 2021 · 4 comments · Fixed by #724

Comments

@kensel
Copy link

kensel commented Mar 11, 2021

Is there a way or better tool that can have the client send updates to Gatus.

For example having a cron job that executes a curl against http(s)://gatus.example.com/client/{computer name}/{service name}/{check}

With a monitor that if the check for heartbeat hasn’t been received in 10 minutes it will generate an alert? This would make it possible for systems only allowed to send out but not in based on network segmentation to provide updates.
Thank you,
Kensel

@TwiN
Copy link
Owner

TwiN commented Mar 12, 2021

@kensel Would #64 fulfill your needs? It's one of the features I've been contemplating working on in the near future.

@kensel
Copy link
Author

kensel commented Mar 12, 2021

#64 has a similar reasoning with segmented networks but I think it doesn't quite make sense when you are looking at 50 micro segments with 2-3 systems on it having to deploy another system to host the Gatus sub nodes. I guess it wold also depend on the reasoning where as #64 would be monitoring systems on the nodes I'm just looking for confirmation the nodes are up.

In regards to the comments about pulling vs. pushing I agree when transferring data like metrics that varies and can be large and overload the monitoring system. The different arguments play out with Prometheus(pull) vs Influx(push). But for small regular pings the data isn't the important part and could be just the fact that there was http request in the first place, it is the time between the pings that becomes important. If we can have clients push it would make it possible with an internet accessible Gatus endpoint to setup systems that can be turned on and ping back without regards for the firewall configuration of temporary sites, especially if it is possible for something like a dynamic registration that doesn't require the individual computers to be registered initially.

@TwiN
Copy link
Owner

TwiN commented Sep 14, 2021

This will most likely not be implemented (at least, not in the short term) for the same first reason I gave on #165, however, you can technically do this by leveraging the postgres storage that I merged into master a couple of days ago, even though it's kind of hacky 😅

@TwiN
Copy link
Owner

TwiN commented Jan 4, 2022

Moved to #229

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants