-
Notifications
You must be signed in to change notification settings - Fork 75
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
Add postgresql metrics logging #2799
base: master
Are you sure you want to change the base?
Add postgresql metrics logging #2799
Conversation
|
||
### Logging database statistics | ||
|
||
Database default's log drain will not contain query statistics, which are ephemeral. Plus, you have a limited time to troubleshoot runnings queries, which may not be convenient. To log them and other statistics, such as query statistics, slow queries, database I/O and CPU, you can use our [API](https://developers.scalingo.com/databases/metrics) and log them by yourself using [a scheduler](https://doc.scalingo.com/platform/app/task-scheduling/scalingo-scheduler). An open-source example is [available here](https://doc.scalingo.com/platform/app/task-scheduling/scalingo-scheduler), although not provided by Scalingo itself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@GradedJestRisk did you intend for that last link to go to https://github.com/1024pix/pix-db-stats ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure ! I fixed it.
04cf232
to
1055f36
Compare
Thank for your contribution @GradedJestRisk Sorry to have let it without feedback for so long We are reviewing it right now! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi again, and thanks again for your contribution
At first, you have to know that we are aware of the need for metric drains.
What about moving your addition into the "Monitoring and Auditing" section rather than "Troubleshooting"?
Also, in order to keep links as much internal as possible, would it be possible to replace the link to the example repo with a few links to the documentation of the API endpoints which could be used to gather metrics and statistics?
Problem
Database metrics are scarce and ephemeral. We definitely need more of them offline.
Check this blog post.
Solution
Add these in log drain, using Scalingo API