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

seriesCountLimit is not explained #66526

Closed
olitomlinson opened this issue Nov 23, 2020 · 3 comments
Closed

seriesCountLimit is not explained #66526

olitomlinson opened this issue Nov 23, 2020 · 3 comments

Comments

@olitomlinson
Copy link
Contributor

The below statement does not make sense and fails to convey what the seriesCountLimit configuration option represents.

  • seriesCountLimit is the max number of data time series a metric can contain. Once this limit is reached, calls to TrackValue().

Please provide an explicit example on how seriesCountLimit can be exceeded. In a similar manner to the example of how valuesPerDimensionLimit is exceeded.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@MonikaReddy-MSFT
Copy link
Contributor

@olitomlinson -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

@gorillapower
Copy link

I found these tutorials and samples on similar travels which helped with my understanding
microsoft/ApplicationInsights-dotnet#774

@lgayhardt
Copy link
Contributor

Sorry for the delay and thanks for the feedback. I made a PR and added on to the statement you mentioned to make it more clear "seriesCountLimit is the max number of data time series a metric can contain. Once this limit is reached, calls to TrackValue() that would normally result in a new series will return false."

The change should go live tomorrow.

#please-close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants