-
Notifications
You must be signed in to change notification settings - Fork 30
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
Investigate quicker ways to deploy monitoring scripts #271
Comments
Why not make the daemons that expose Prometheus metrics directly, rather than write out to the node_exporter? |
@SuperQ it would make the daemons significantly more complex, having to run a dedicated thread each to expose the metrics, and more burdensome to deploy, having to assign a unique port to each, allow incoming traffic and configure Prometheus to scrape each of them. |
The kinds of monitoring tasks you're talking about are already implemented by good quality code. For example, there are several SQL query exporters for exposing SQL query data. Add monitoring endpoints to existing daemons is not "significantly more complex". These techniques are well documented and common. |
* Fastpath: Add anomaly and confirmed columns * Add workaround for CircleCi bug * Add 019-fastpath-confirmed.rollback.sql * Add msm_failure column, BRIM index, rename indexes * Add missing platform UPDATE SET
Each service is now exposing metrics directly and we are working toward discontinuing netdata in favour of this. I am closing this issue in favour of the several monitoring related ones we have elsewhere: |
Setting up daemons that write to node_exporter is time consuming
We can test netdata plugins after #268
The text was updated successfully, but these errors were encountered: