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

Provider API monitoring #421

Open
5 tasks
alexgeorgousis opened this issue Dec 19, 2024 · 1 comment
Open
5 tasks

Provider API monitoring #421

alexgeorgousis opened this issue Dec 19, 2024 · 1 comment

Comments

@alexgeorgousis
Copy link
Contributor

alexgeorgousis commented Dec 19, 2024

Overview

After #376 all provider logic will be encapsulated in a live service. So, as with any service, we want users to be able to monitor it.

We need to:

  1. Consider which metrics would be valuable for the service to expose
  2. Expose the metrics we've chosen

Chosen Metrics

  • API response status codes (successes and failures)
  • CPU/Memory usage
  • Latency
  • Anything else Provider specific?

Acceptance Criteria

  • Our chosen metrics are being exported by the provider API
@aidandunlop
Copy link
Contributor

We should spin out separate card for the skeleton setup of Service Monitor and basic Prometheus metrics for the Provider service

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