-
Notifications
You must be signed in to change notification settings - Fork 77
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
Instrument the application #2
Comments
also probably disk usage as |
Yes. The disk usage for |
Note that issues like huggingface/datasets#2859 can affect the CPU and memory usage (even block the server completely) |
Two solutions proposed by the infra team: https://huggingface.slack.com/archives/CTKK32GE8/p1630588820038000 Morgan: We have been using Prometheus with success to report this kind of metrics on the Inference API.
Philip: You could also use directly cloudwatch with either the:
AFAIK most of our production service are using prometheus + grafana sofar, with ELK as additional informations. So you could directly log into the existing system for this already |
See how prometheus is used in other projects:
As we rely on Starlette, we might want to try https://github.com/perdy/starlette-prometheus |
Also: alert when 500 errors occur. See #21 (comment) |
Best practices on what to monitor: https://prometheus.io/docs/practices/instrumentation |
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
Already in place. Let's improve when needed |
Measure the response time, status code, RAM usage, etc. to be able to take decision (see #1). Also statistics about the most common requests (endpoint, dataset, parameters)
The text was updated successfully, but these errors were encountered: