You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expose the raw uptime data at a per-monitor level via an API endpoint which can be consumed by other applications, unlike the current badges.
Why do you personally want this feature to be implemented?
We use Gatus as our status dashboard and monitoring solution. As a team we want to report monthly uptime on our self-hosted production systems as a KPI, but Gatus can only report 7 day uptime data. I've seen various discussions around increasing the data retention and reporting to 30 days and beyond, but given the challenges presented it seems difficult at this time.
Instead I'd like to expose the uptime data in it's raw format so that I can create a small application to consume the data on a daily basis, then calculate uptime data for a specific month.
How long have you been using this project?
Over 1 year
Additional information
No response
The text was updated successfully, but these errors were encountered:
Describe the feature request
Expose the raw uptime data at a per-monitor level via an API endpoint which can be consumed by other applications, unlike the current badges.
Why do you personally want this feature to be implemented?
We use Gatus as our status dashboard and monitoring solution. As a team we want to report monthly uptime on our self-hosted production systems as a KPI, but Gatus can only report 7 day uptime data. I've seen various discussions around increasing the data retention and reporting to 30 days and beyond, but given the challenges presented it seems difficult at this time.
Instead I'd like to expose the uptime data in it's raw format so that I can create a small application to consume the data on a daily basis, then calculate uptime data for a specific month.
How long have you been using this project?
Over 1 year
Additional information
No response
The text was updated successfully, but these errors were encountered: