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

/stats endpoint #131

Open
gmelodie opened this issue Oct 13, 2022 · 1 comment
Open

/stats endpoint #131

gmelodie opened this issue Oct 13, 2022 · 1 comment

Comments

@gmelodie
Copy link
Contributor

We should have a way to get stats from autoretrieve. The ones I'd personally like are:

  • when was the last successful estuary heartbeat
  • was the last estuary heartbeat failed?
  • how many retrievals we did in the last hour

Not sure if we already have something like this

@rvagg
Copy link
Collaborator

rvagg commented Oct 14, 2022

We don't, not directly from autoretrieve anyway. But when plugged into a prometheus backend we get a ton of stats, as of this week's changes we're even down to getting specifics on errors:

Screenshot 2022-10-14 at 1 44 54 pm

I imagine it wouldn't be too hard to get something similar set up for Estuary's autoretrieve instance and adding in those additional heartbeat metrics wouldn't be hard (see this week's changes for examples).

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

No branches or pull requests

2 participants