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

Revert "Modify regexes to match both deprecated and new metrics in 1.16" #391

Merged
merged 2 commits into from Feb 4, 2020

Conversation

maimaisie
Copy link
Contributor

Reverts #372 since this we have another minor release to make before the major release

Copy link
Contributor

@rvmiller89 rvmiller89 left a comment

Choose a reason for hiding this comment

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

We could technically keep this right?

@maimaisie
Copy link
Contributor Author

The changed regexes match both deprecated and renamed metrics, and on 1.16 both sets of metrics are being generated and collected by fluentd if we keep this change. At least one of the metrics has very high cardinality and the increase in DPM is a concern. I'm still talking to Frank if we want to fix this and how for the major release

@maimaisie maimaisie force-pushed the revert-372-maisie-metric-renames branch from c5d06c2 to 7f6ee32 Compare February 3, 2020 22:10
@maimaisie maimaisie force-pushed the revert-372-maisie-metric-renames branch from 7f6ee32 to 3e8c149 Compare February 4, 2020 00:49
@maimaisie maimaisie merged commit dd3ce22 into master Feb 4, 2020
@maimaisie maimaisie deleted the revert-372-maisie-metric-renames branch February 4, 2020 01:16
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.

None yet

2 participants