Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upPromtail extraScrapeConfigs not being picked up #2068
Comments
|
After a bit more research we came up with the following that did work:
Which feels very hacky and unsustainable, since we have to copy the default, modify it and then overwrite it. Is this intended behaviour? |
|
I guess it's because extraScrapeConfigs is at the end and not at the beginning ? It this was the problem I'm ok to receive a PR to move it to the top, because you're right if you want to drop targets this is useless. Can you confirm that this was the problem ? |
|
I think that would solve the problem, will make a PR soon. |
|
You mean a PR ;) |
|
To clarify: the example on top is to exclude a namespace, we eventually wanted to exclude pod logs with:
inside the existing kubernetes-pods-app scrape job. This did work. |
|
Were you able to exclude logs for a specific pod? I've tried with the following within the existing "kubernetes-pods-app" job but with no luck: - action: drop Maybe you can share with me how your "kubernetes-pods-app" looks like? Thanks. |
|
Yes, it should work like this:
|
|
Thanks, this seems to be working fine. |


Describe the bug
It seems that excluding logs in a namespace using the configuration below does not work:
To Reproduce
Steps to reproduce the behavior:
{namespace="namespace_name"}in Grafana LokiExpected behavior
Not seeing any logs
Environment:
Maybe i'm missing something, help would be appreciated!