improve the name of the prometheus metrics #995
Merged
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.
What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
What this PR does / why we need it:
With its recent releases, Falco comes now out of the box with prometheus metrics, all the metrics follow the convention
falcosecurity_<project>_<metric>_<type>
.project
represents the project, it can befalco
,falcosidekick
(goal of this PR),talon
, ...This PR introduces the prefix
falcosecurity
, addfalcosidekick
as project, and thetype
astotal
(all metrics are counters for now)To be compliant with the labels used by
falco
and be compliant with the already existing rules from the falco-exporter, the labelpriority
has been changed topriority_raw
andpriority
now contains an int.Warning
By changing the names, this PR introduces a breaking change. All dashboards or configured alerts will have to be updated, the Changelog and the blog post following the next release will explain that for the end users.
Which issue(s) this PR fixes:
#940
Fixes #
Special notes for your reviewer: