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

cmd,query: bump promql-engine and make subqueries for thanos engine configurable #6648

Conversation

MichaHoffmann
Copy link
Contributor

@MichaHoffmann MichaHoffmann commented Aug 24, 2023

  • I added CHANGELOG entry for this change.
  • Change is not relevant to the end user.

Changes

Bumped promql-engine; fixed fallout from the bump; added a configuration flag for enabling subqueries in the thanos engine

Verification

Not tested yet.

@MichaHoffmann MichaHoffmann force-pushed the mhoffm-bump-promql-engine-make-subqueries-configurable branch 2 times, most recently from 94233c0 to e5ec239 Compare August 24, 2023 09:28
…onfigurable

Signed-off-by: Michael Hoffmann <mhoffm@posteo.de>
@MichaHoffmann MichaHoffmann force-pushed the mhoffm-bump-promql-engine-make-subqueries-configurable branch from e5ec239 to bf89e7d Compare August 24, 2023 09:28
engine.Opts{
EngineOpts: engineOpts,
Engine: promql.NewEngine(engineOpts),
EnableSubqueries: enableThanosEngineSubqueries,
Copy link
Contributor

Choose a reason for hiding this comment

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

Feel like it is an overkill to me to have a flag for it

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I added it by popular request to have this feature configurable ( for a short time ). Once this has proven stable enough we can probably remove the flag again.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Having said that im fairly confident that it works like in upstream promql since it passes acceptance tests and fuzzing

Copy link
Member

Choose a reason for hiding this comment

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

➕ maybe we can just enable subqueries? The more people exposed to this, the faster bugs will be fixed (if any)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sadly subqueries are super prevalent in our alerting pipeline; if it has a bug we would need to quickly roll it back. I would prefer the switch because it would be critical for us if this has an issue.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Can we have it for a short time and we run a nightly build and once we are happy ill take out the switch again?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I guess we could use prometheus engine in case of issues too, so maybe its not so bad.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Consulted with a teammate; ill take out the flag in a couple hours!

@yeya24
Copy link
Contributor

yeya24 commented Aug 28, 2023

@MichaHoffmann
Copy link
Contributor Author

Can we take a look at the failed unit test? https://app.circleci.com/pipelines/github/MichaHoffmann/thanos/79/workflows/475701d9-0860-424d-8f75-ccb828384599/jobs/83

Oh thats maybe related to the prometheus version bump and looks a bit scary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants