We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
we have an issue with the app metrics library.
The Field value sometimes it is sometimes 1 and sometimes it is 0 with the same metric name Ex: {"value": 0}
My application is related to .Net 6.0. we saw duplicate metrics.
we are reporting the metrics over HTTP and using the counters.
fields={"value": 0}, time=1695618192502931600).
why is this library pushing duplicate metrics with different field values?
options.HttpPolicy.BackoffPeriod = TimeSpan.FromSeconds(30); options.HttpPolicy.FailuresBeforeBackoff = 5; options.HttpPolicy.Timeout = TimeSpan.FromSeconds(10); options.MetricsOutputFormatter = new MetricsInfluxDbLineProtocolOutputFormatter(); options.FlushInterval = TimeSpan.FromSeconds(15);
Please point us to the correct direction.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
we have an issue with the app metrics library.
The Field value sometimes it is sometimes 1 and sometimes it is 0 with the same metric name Ex: {"value": 0}
My application is related to .Net 6.0. we saw duplicate metrics.
we are reporting the metrics over HTTP and using the counters.
fields={"value": 0}, time=1695618192502931600).
why is this library pushing duplicate metrics with different field values?
options.HttpPolicy.BackoffPeriod = TimeSpan.FromSeconds(30);
options.HttpPolicy.FailuresBeforeBackoff = 5;
options.HttpPolicy.Timeout = TimeSpan.FromSeconds(10);
options.MetricsOutputFormatter = new MetricsInfluxDbLineProtocolOutputFormatter();
options.FlushInterval = TimeSpan.FromSeconds(15);
Please point us to the correct direction.
The text was updated successfully, but these errors were encountered: