Skip to content
This repository has been archived by the owner on Mar 27, 2021. It is now read-only.

Add cluster analytics/stats endpoint to the API #714

Open
hexedpackets opened this issue Oct 27, 2020 · 3 comments
Open

Add cluster analytics/stats endpoint to the API #714

hexedpackets opened this issue Oct 27, 2020 · 3 comments

Comments

@hexedpackets
Copy link
Contributor

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:

  • number of active requests by endpoint
  • requests that have been running for over a set amount of time (similar to something like pg_stat_statements)
  • echo back current config
  • information on the various pipeline connections (PubSub, Cassandra, BigTable)

As an example for comparison, OpenTSDB has an endpoint that returns all active queries and the 256 most recently completed ones.

@sming
Copy link
Contributor

sming commented Oct 27, 2020

Hi William, is this part of Heroic Stability work?

@hexedpackets
Copy link
Contributor Author

@sming Not directly, although having this kind of data would help us make more informed decisions when prioritizing our efforts.

@sming
Copy link
Contributor

sming commented Oct 27, 2020

Yes, it looked like a "supporting cast" kind of ticket. Will message you on Slack.

@lmuhlha lmuhlha removed this from Inbox in Observability Kanban Oct 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants