-
Notifications
You must be signed in to change notification settings - Fork 101
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
Document scenarios for sending graphite metrics to graphite_exporter #74
Comments
Yes, how you send metrics to the exporter is up to you. You can do this in your code, or use carbon-relay. For the best results, I would recommend running the exporter and (if necessary) carbon-relay as sidecars, that is, local to each application instance:
This gets you better (per-instance) metrics in a Prometheus-native way. Additionally, by tying the metric producer and the exporter together, you avoid a few classes of issues with inconsistent metrics. |
I think this could be explained better in the README. I'll update the issue title to reflect that. |
@matthiasr thank you very much for your detailed answers and I also think that this information needs to be added to the README. I will try it and consult with you if i have any question. |
Hi all:
I tried graphite_exporter for the first time. I have graphite and graphite_exporter running on different hosts already, but how can i send the metrics which graphite received to the graphite_exporter? Is there a way to config this or must i write codes to achieve this goal ? In graphite , I only run carbon-cache. should I run carbon-relay or carbon-agg to send metrics to graphite_exporter?
can someone tell me how to do it ? appreciate it
The text was updated successfully, but these errors were encountered: