add StorePerformanceLabelAsField and StoreCommandAsField options #42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
On big monitoring environments with tons of checks with variable performanceLabel (like disk label on disk checks or interface labels on network interface checks, etc.) the cardinality of the performanceLabel tag explodes.
This causes each write to become slower and slower and memory allocation increases.
Storing the performanceLabel as Field instead of a Tag in InfluxDB has proven to decrease load a lot in such situations.
This pull requests adds two options for storing the performanceLabel as a Field: