FluentD debug tracing about oms-agent-for-linux HOT 4 CLOSED

While it's not difficult modifying service_control to take a debug level, note that the various mechanisms used to start across various systems (be it /etc/inid.d style scripts or systemd control) do not necessarily take a parameter. I could set something globally and detect at startup, but that seems kind of sloppy to me.

As for the -vv option to fluentd, we're using the fluentd framework, and we're checking for debug of our particular plugin. Debugging globally (what -vv does) doesn't appear to set individual plugins to debug, which is why that's happening.

Given what you're after, I think it's easier just to change the configuration to debug our plugin.

Hope this helps,

/Jeff

from oms-agent-for-linux.

To answer the second part of the question, there are two types of log levels in fluentd:

1. The global logging level controlled on invocation with the -v or -vv flags affects $log.
2. The per plugging logging level controlled by the log_level tag in the configuration script affects @log.

In this case per plugin logging is used. Change the log_level of the output plugin to debug. The configuration file is located in /etc/opt/microsoft/omsagent/conf/omsagent.conf
Additional documentation can be found here : http://docs.fluentd.org/articles/logging#per-plugin-log

from oms-agent-for-linux.

@ChrisHeitkamp, have we answered your questions? If so, please feel free to close this issue. If not, please post a new comment and we'll help you out.

from oms-agent-for-linux.

@jeffaco @niroyb, thanks, this was the information I needed.

from oms-agent-for-linux.