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

Metrics drop #6

Closed
graineri opened this issue Sep 14, 2017 · 4 comments
Closed

Metrics drop #6

graineri opened this issue Sep 14, 2017 · 4 comments

Comments

@graineri
Copy link

graineri commented Sep 14, 2017

I have just setup a statsdcc-proxy with two statsdcc-aggregators and one carbon backend.

After doing this, the metrics dropped to nearly a quarter as they used to be when I had a single statsdcc-aggregator.

I guess that the proxy is hashing the metric so that the same metric is always received by the same statsdcc-aggregator. So, that shouldn't be a problem.

It also seems that I'm losing metrics from certain application nodes that I used to have before adding the proxy.

Any ideas why I'm facing this behavior?

@sdomalap
Copy link
Collaborator

Proxy does calculate integer hash of the metric name. It's some processing in the order of length of metric names.

You can scale proxy by increasing the number of worker threads.

Are you running all of them on the same host? How is your CPU utilization look?

@graineri
Copy link
Author

I'm running each of them on separate instances. Each instance has 4 cores and are quite idle in terms of processing. So, that should be fine.

@graineri
Copy link
Author

I might be using the original code without the MSG_SIZE fix. Let me check everything and get back to you.

@graineri
Copy link
Author

False alarm. Totally my fault. I was using the previous version without the fix. I'm sorry about this.

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

No branches or pull requests

2 participants