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
{{ message }}
This repository has been archived by the owner on Mar 27, 2021. It is now read-only.
Right now its hard to discover information about how a Heroic cluster is being used, requiring something like a separate QueryLog analytics setup. Some of this information is actually pretty discoverable within Heroic itself, and just needs a decent way of querying it.
Right now its hard to discover information about how a Heroic cluster is being used, requiring something like a separate QueryLog analytics setup. Some of this information is actually pretty discoverable within Heroic itself, and just needs a decent way of querying it.
We already have an API endpoint that can return the total number of active timeseries. Some other possibilities that have varying levels of difficulty:
As an example for comparison, OpenTSDB has an endpoint that returns all active queries and the 256 most recently completed ones.
The text was updated successfully, but these errors were encountered: