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

Falcosidekick PrometheusRule query failing #667

Closed
ashtongraves opened this issue May 10, 2024 · 5 comments
Closed

Falcosidekick PrometheusRule query failing #667

ashtongraves opened this issue May 10, 2024 · 5 comments
Assignees
Labels
kind/bug Something isn't working

Comments

@ashtongraves
Copy link

This is for the falcosidekick prometheus rules. Prometheus doesn't like the query you have for the FalcoErrorOutputEventsRateHigh alert.

When I run this in my prometheus instance I get: Error executing query: invalid parameter "query": 1:48: parse error: unexpected <by>

I'm running Prometheus 2.45.0

How to reproduce it

Run rate(falcosidekick_output{status="error"}[5m]) by (destination) > 0 in prometheus

Expected behaviour

I expect it to run the query without error

Environment

I'm running via the sidekick chart bundled with the falco chart.

- app_version: 0.37.1
  description: Falco
  repository:
    name: falcosecurity
    url: https://falcosecurity.github.io/charts
  url: https://artifacthub.io/packages/helm/falcosecurity/falco
  version: 4.3.0

Prometheus 2.45.0

Additional context

@ashtongraves ashtongraves added the kind/bug Something isn't working label May 10, 2024
@Issif
Copy link
Member

Issif commented May 13, 2024

This issue has been fixed in the PR #643 but the dependency to Falcosidekick hasn't been updated in the Falco chart.yaml. Do you feel confident to propose the PR yourself?

@Issif Issif self-assigned this May 13, 2024
@ashtongraves
Copy link
Author

This issue has been fixed in the PR #643 but the dependency to Falcosidekick hasn't been updated in the Falco chart.yaml. Do you feel confident to propose the PR yourself?

Sorry thought I replied. But that PR just fixes one of two issues preventing me from installing the prometheus rule. So yes fixing the duplicate prometheus rule name is one issue, the other I'm having is with the query erroring out on prometheus. I don't believe that one is fixed yet, unless it's some prometheus version issue or something.

@Issif
Copy link
Member

Issif commented May 21, 2024

We'll fix that, thanks for the notice.

@ArnaudCHT
Copy link
Contributor

Hello, this PR should fix the problem :

#670

@Issif Issif closed this as completed May 21, 2024
@ashtongraves
Copy link
Author

Hello, this PR should fix the problem :

#670

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants