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

includeNamespace meaning #410

Open
fabianboerner opened this issue Dec 29, 2023 · 3 comments
Open

includeNamespace meaning #410

fabianboerner opened this issue Dec 29, 2023 · 3 comments

Comments

@fabianboerner
Copy link

the setting includeNamespace doesnt mean namespaces but container names?

For me the namespace name stopped all logs from beeing shipped.

@mirii1994
Copy link
Contributor

Hi @fabianboerner ,
Can you please share how you configured this variable?
Each container is represented in a log file in the node. The log file's name contains (among other things), the namespace. This is why in the instructions we wrote:

Use if you wish to send logs from specific k8s namespaces, space delimited. Should be in the following format: kubernetes.var.log.containers.**_<<NAMESPACE-TO-INCLUDE>>_** kubernetes.var.log.containers.**_<<ANOTHER-NAMESPACE>>_**.

Then this value is being used in our output plugin, to filter only logs with those tags.

@fabianboerner
Copy link
Author

fabianboerner commented Dec 31, 2023

i used "kubernetes.var.log.containers.namespace"

should it be "kubernetes.var.log.containers.**_namespace_** ?

@mirii1994
Copy link
Contributor

@fabianboerner exactly, it should be kubernetes.var.log.containers.**_namespace_**.

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

No branches or pull requests

2 participants