PrometheusRule priority does not match metrics priority

[jkrusy]

Describe the bug

The Falcosidekick metrics priority does not match with the priority in the PrometheusRule. Metrics are provided and scraped like following:

falco_events{priority="Critical",rule="Drop and execute new binary in container"} 1

But the prometheusrule expects the priority to be a number:

        - alert: FalcoWarningEventsRateHigh
          annotations:
            description: A high rate of warning events are being detected by Falco
            summary: Falco is experiencing high rate of warning events
          expr: rate(falco_events{priority="4"}[5m]) > 0

With this combination, the rules will not work.

How to reproduce it

Here is the configuration we have

falco:
  priority: warning
  log_level: warning

falcosidekick:
  enabled: true
  serviceMonitor:
    enabled: true
  prometheusRules:
    enabled: true
    warning:
      enabled: true
    critical:
      enabled: true

Expected behaviour

The prometheus rules should match the metrics provided by Falcosidekick.

Screenshots

Environment

• Falco version:

  {"default_driver_version":"7.0.0+driver","driver_api_version":"8.0.0","driver_schema_version":"2.0.0","engine_version":"31","engine_version_semver":"0.31.0","falco_version":"0.37.1","libs_version":"0.14.3","plugin_api_version":"3.2.0"}

• System info:

  {
  "machine": "x86_64",
  "nodename": "falco-falco-lf2gq",
  "release": "5.10.215-203.850.amzn2.x86_64",
  "sysname": "Linux",
  "version": "#1 SMP Tue Apr 23 20:32:19 UTC 2024"
  }

• Cloud provider or hardware configuration: AWS EKS
• OS: linux (amd64) [Amazon Linux 2]
• Kernel: 5.10.214-202.855.amzn2.x86_64
• Installation method: Kubernetes Helm Chart