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
vmagent: wrong relabeling via -remoteWrite.urlRelabelConfig #599
Comments
@Allineer , could you add |
@valyala, no other metrics atm. self-scraping is disabled. |
vmagent's logs:
I have 20-30 messages with this error daily. |
The last graph looks really weird - I'm still investigating this issue... It looks like some data race or improper cleanup of reused structures during relabeling. |
I have a really extensive |
…ig` options are set Previously multiple goroutines could access remoteWriteCtx.tss concurrently, which could lead to data race and improper relabeling. Now each goroutine has its own copy of tss during relabeling. Updates #599
…ig` options are set Previously multiple goroutines could access remoteWriteCtx.tss concurrently, which could lead to data race and improper relabeling. Now each goroutine has its own copy of tss during relabeling. Updates #599
@Allineer , the commit a730b3f should fix the issue. Could you try building |
|
Already testing... |
It's working! Thanks! |
Describe the bug
-remoteWrite.urlRelabelConfig
:I see metrics for other jobs and agents in the database:
another
-remoteWrite.urlRelabelConfig
:Expected behavior
Correct filtering.
Version
The text was updated successfully, but these errors were encountered: