Skip to content

Improved sink debugging flow.#821

Merged
bwplotka merged 2 commits intomasterfrom
prw2
Jan 31, 2025
Merged

Improved sink debugging flow.#821
bwplotka merged 2 commits intomasterfrom
prw2

Conversation

@bwplotka
Copy link
Copy Markdown
Member

@bwplotka bwplotka commented Jan 31, 2025

This improves PRW benchmark flow by:

  • Adding PRW 2.0 traffic which we should care about with the next Prometheus releases. We could drop PRW 1.0 communication given no development on that path, but since ppl still use it, let's keep it. I removed it for now as it depends on metadata-wal-records feature which is problematic currently: Deprecate and ultimately remove metadata-wal-records feature enabled. prometheus#15911
  • Updating sink with the latest issue handling features.
  • Creating different configmap for each Prometheus in the same file. This is to ensure we have pass a different PRW header so in the sink we will know which issue belongs to what Prometheus (e.g. prometheus from the PR is suddenly not sending help).
  • Meta Prom scrapes now sink

@ArthurSens
Copy link
Copy Markdown
Member

ArthurSens commented Jan 31, 2025

Would you like to try running a custom benchmark from this branch to make sure it works?

bwplotka added a commit to prometheus/prometheus that referenced this pull request Jan 31, 2025
@bwplotka
Copy link
Copy Markdown
Member Author

I didn't plan this, no - wanted to spend my time somewhere else (low risk, low impact, can be fixed in seconds) 🙃

But given you pointed out, let's do this: prometheus/prometheus#15914

@bwplotka
Copy link
Copy Markdown
Member Author

Well glad you did asked for it

2025-01-31 13:09:29.996 GMT
time=2025-01-31T13:09:29.996Z level=ERROR source=main.go:1465 msg="Failed to apply configuration" err="invalid remote write configuration, if you are using remote write version 2.0 the --enable-feature=metadata-wal-records feature flag must be enabled"

(:

@bwplotka bwplotka changed the title Added PRW 2.0 traffic, improved sink debugging flow. Improved sink debugging flow. Jan 31, 2025
@bwplotka
Copy link
Copy Markdown
Member Author

bwplotka commented Jan 31, 2025

Removed PRW2 comms for now as it depends on metadata-wal-records feature which is problematic currently: prometheus/prometheus#15911

@bwplotka
Copy link
Copy Markdown
Member Author

Tested prometheus/prometheus#15914 works now.

Copy link
Copy Markdown
Member

@ArthurSens ArthurSens left a comment

Choose a reason for hiding this comment

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

Thanks! Idea for the future: adding the new sink metrics/logs to a separate dashboard :)

@bwplotka bwplotka merged commit 4ff03e0 into master Jan 31, 2025
@bwplotka bwplotka deleted the prw2 branch January 31, 2025 14:32
Copy link
Copy Markdown
Member

@kakkoyun kakkoyun left a comment

Choose a reason for hiding this comment

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

LGTM

@bboreham
Copy link
Copy Markdown
Member

bboreham commented Feb 5, 2025

Why did the filenames change?
e.g. 3b_prometheus-test-pr_deployment.yaml -> 3_prometheus-test-pr_deployment.yaml

kushalShukla-web pushed a commit to kushalShukla-web/test-infra that referenced this pull request Feb 8, 2025
* Add PRW 2.0 traffic, improved sink debugging flow.

Signed-off-by: bwplotka <[email protected]>

* Removed PRW 2.0 as it depends on expensive metadata-wal-records feature.

Signed-off-by: bwplotka <[email protected]>

---------

Signed-off-by: bwplotka <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants