This message was deleted.
# logging
a
This message was deleted.
l
can you confirm these changes have made it into the actual fluentd config?
there is a secret with the config, but also the configcheck pod output should reflect the change
also you can try to restart the fluentd pods to see if the reload failed
p
Yes, the changes have been applied and appear in the “logging-root-fluentd-app” secret:
Copy code
<route>
    @label @90659d5096f28c1fda0335b03c332d94
    metrics_labels {"id":"clusterflow:cattle-logging-system:logstash-flow-etd"}
    <match>
      container_names vault-agent-init,vault-agent
      namespaces xxx
      negate true
    </match>
    <match>
      labels team:etd
      negate false
    </match>
  </route>
I saw the detection of the configuration change in the pod logs too. I've already tried restarting all the pods but still the same, the “vault-agent-init” and “vault-agent” container logs continue to be transmitted in Syslog.
l
this is the only flow/clusterflow you have?
p
OK I found the problem, I had put an exclusion on namespaces and container_names in the same “exclude” when I should have separated them into two different “exclude”... Sorry for the inconvenience, another problem between the chair and the keyboard! :D
l
hey, glad that you could figure that out! 🙂