Orchestrator Log Files

[ririmia]

Hello,

I'm forwarding all the vRO logs to a Syslog server and I want to reduce the amount of logs.

vRO 7.5.0.10044239

I need to know more information related to 'metrics.log' and 'vc-metrics.log'

/var/log/vco/app-server/metrics.log

According to the documentation this log "contains runtime information about the server. The information is added to this log file once every 5 minutes."

I saw that "metrics.log" is updated once every 1 minute instead.

There is any setting that can control this behavior?

Can this logs be stopped?

All the logs are related to statistics that I'm not interested to keep them on a Syslog server.

Thank you.

[iiliev]

Hi,

You cannot control the duration of logging interval - I think it is hard-coded in a configuration file that is embedded into one of vRO platform binaries.

What you can control, however, is the log level of the logged messages. By default I think all messages with level INFO or above are logged (INFO/WARN/ERROR/FATAL), but you can change the level in /etc/vco/app-server/log4j.xml configuration file from INFO to some higher level, or even to OFF to turn off the logging for this category. Setting the log level to some value will disable log requests that have smaller log levels.

[ririmia]

I've changed the /etc/vco/app-server/log4j.xml configuration

.....

    <!-- vRO  metrics log -->

    <category additivity="false" name="metrics">

        <priority value="OFF"/>

        <appender-ref ref="METRICS"/>

    </category>

    <!-- vCenter plugin Metrics log -->

    <category additivity="false" name="vc-metrics">

        <priority value="OFF"/>

        <appender-ref ref="VC-METRICS"/>

    </category>

....

Restart the vCO (service vco-server restart  and  service vco-configurator restart)

After reboot the file /etc/vco/app-server/log4j.xml reverted to the original state. Nothing changed.

[iiliev · Accepted solution]

Is this a clustered vRO setup?

vRO has a command line tool that allows to update the configuration settings from the local file system. Could you try the following command after you change the log4j.xml file but before service restart?

/var/lib/vco/tools/configuration-cli/bin/vro-configure.sh sync-local

[ririmia]

No. It's not a cluster setup.

The command line did the trick. The log4j.xml is persistent and the logging is stopped.

Thank you.