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

Additional Metrics #66

Merged
merged 4 commits into from
Apr 13, 2018
Merged

Additional Metrics #66

merged 4 commits into from
Apr 13, 2018

Conversation

elubow
Copy link
Contributor

@elubow elubow commented Apr 12, 2018

This pull request includes laying out all the metrics for:

  • masters
  • agents
  • /monitor/statistics

Copy link
Contributor

@philipnrmn philipnrmn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome work, thanks @elubow.

@philipnrmn philipnrmn merged commit 4e278f4 into mesos:master Apr 13, 2018
@elubow elubow deleted the new_metrics branch April 13, 2018 14:56
@StephanErb
Copy link
Collaborator

StephanErb commented Apr 13, 2018

-1 on this. This will break every existing deployment that uses this exporter.

If you want to make changes like this, please provide a metric relabeling config so that users can seamlessly migrate all dashboards and alerting configurations.

@philipnrmn
Copy link
Contributor

@StephanErb how so?

@elubow
Copy link
Contributor Author

elubow commented Apr 13, 2018

I only had 1 existing deployment to test it on and it didn't break it. I'm also following this up with another PR which has much better error handling.

@StephanErb
Copy link
Collaborator

StephanErb commented Apr 13, 2018

For example, the metric mem_rss_bytes was renamed to mesos_agent_mem_rss_bytes. I totally agree that the new name is better, but it is very hard to deploy into a production environment with dozens of dashboards and alert configurations.

Normally changes like this are done by providing a metric relabelling config, so that both metrics can co-exist at the same time. For example, there is currently a similar issue in the Prometheus node exporter prometheus/node_exporter#830

@StephanErb
Copy link
Collaborator

I did not intend to sound so harsh. Besides of the breaking naming change this contribution looks great! I am sure we can figure it out :)

@elubow
Copy link
Contributor Author

elubow commented Apr 13, 2018

Part of the issue here is that some of the metrics aren't even being collected all the time. For instance threads is a really generic name. So I'm not sure how a relabel would help there as it's so generic it might actually make things worse depending on the environment. I can certainly create a diff of metric names. But that also won't account for metrics that have migrated to submetrics with labels. At least I couldn't see a way to handle that scenario from prometheus/node_exporter#830. Any solution we come up with would be half-baked at best.

Also, it's only harsh until constructive feedback transpires :) Point taken, but we definitely have some issues that I don't see a path to resolution for.

@philipnrmn
Copy link
Contributor

philipnrmn commented Apr 13, 2018

Not at all harsh - this is very fair criticism, I was trigger-happy on the merge. I'll make sure we get a relabelling config in soon.

ryodocx pushed a commit to ryodocx/mesos_exporter that referenced this pull request Mar 18, 2019
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

Successfully merging this pull request may close these issues.

3 participants