Configure Logging

Log location: /usr/share/apache-tomcat/logs

Primary log file: catalina.out

To change the logging level for the Moogsoft Onprem servlets which run in Tomcat, edit the relevant files in $MOOGSOFT_HOME/config/logging/servlets.

vi $MOOGSOFT_HOME/config/logging/servlets/moogsvr.log.json

...
    "loggers": {
        "Logger": {
            "name": "com.moogsoft",
            "additivity": false,
            "AppenderRef": [{
                "ref": "STDOUT"
            }],
            "level": "info"
        }
    }
...

Log location: /var/log/nginx

Primary log file: error.log

To change the logging level for Nginx:

By default Moogfarmd and Ticketing integrations write logs into a log file stored in /var/log/moogsoft if you have write permissions for this directory. Otherwise, the logs are written to $MOOGSOFT_HOME/log. By default the log file takes the name of the HA address of the process. For example, MOO.moog_farmd.farmd_instance1.log.

MOO is the default HA cluster name in $MOOGSOFT_HOME/config/system.conf. If you change it the Moogfarmd log file path changes accordingly.

Restart Moogfarmd after making any of the following configuration changes.

To use a custom log configuration file for Moogfarmd:

To change the logging level for Moogfarmd, edit the file $MOOGSOFT_HOME/config/logging/moog_farmd.log.json. For example:

"configuration":
{
    "ThresholdFilter": 
    {
        "level": "trace"
    },
}

You can also modify the log level using moog_farmd --loglevel. There are two options:

Adjusting moogfarmd log level (moog_farmd.log.json):

vi $MOOGSOFT_HOME/config/logging/moog_farmd.log.json

...
            "Logger": [
                {
                    "name": "com.moogsoft",
                    "additivity": false,
                    "AppenderRef": [{
                       "ref":"${sys:MoogsoftLogAppender}"
                    }],
                    "level": "info"
}
...

See Moogfarmd Reference for more information.Moogfarmd Reference

To save Moogfarmd logs to a different location and/or filename, edit the Moogfarmd log configuration file located at $MOOGSOFT_HOME/config/logging/moog_farmd.log.json. For example:

"RollingFile": 
{
    "name"     : "FILE",
    "fileName" : "/var/log/moogsoft/Moogfarmd_test.log"
}

LAMs and monitoring integrations log their processing and data ingestion to two types of log files, process and capture. Ticketing integrations do not have dedicated log files, and instead log their processing and data to var/log/moogsoft/MOO.moog_farmd.log. For more information, refer to the preceding section on Moogfarmd.

WARN : [target1][20190117 13:03:33.942 +0000] [CZabbixPollingTask.java:129] +|40001: An error response received 
from Zabbix REST server: [Invalid URL provided [http://zabbixserver1/zabbix/api_jsonrpc.php] for User Login request]|+

Failed Connection Attempt for target [target1] and destination [http://zabbixserver1/zabbix/api_jsonrpc.php]. This is attempt [1] out of [infinite].

Failed Connection Error [rabbitmq-host.com: nodename nor servname provided, or not known]. This is attempt [2] out of [infinite].

agent:
{
    name        : "SolarWinds",
    capture_log : "$MOOGSOFT_HOME/log/data-capture/solarwinds_lam.log"
}

Log location: /var/log/mysqld.log

MySQL logging defaults to the highest level. To remove warnings from the MySQL log:

Log location: /var/log/rabbitmq

Refer to the RabbitMQ documentation for information on how to configure RabbitMQ.

Log location: /var/log/opensearch/moog-opensearch-cluster.log.

Refer to the OpenSearch documentation for information on how to configure OpenSearch.

Moogsoft Onprem uses two libraries for persistence: Hazelcast and Kryo. You can configure the logging for these components in the file $MOOGSOFT_HOME/config/logging/moog_farmd.log.json.

The logging level is set to WARN by default. Logs are written to the process log file.

When you create, update and delete topologies and their nodes and links, Apache Tomcat logs the details in its primary log file catalina.out. An example log entry at INFO level is as follows:

INFO : [Topologies Reporter Thread][20200225 16:48:25.105 +0000] [CReporterThread.java:142] +|Topologies server handled [200] topologies requests in the last [60] seconds.|+

Example errors at WARN level:

“Unable to replace topology as topology to be replaced is not valid: [physical]" (WARN)
"Unable to replace topology [physical] as replacing topology is not valid: [network] (WARN)
"Unable to replace topology [%s] - topology [%s] has not been updated" (WARN)
"Failed to get all nodes for topology [physical] as it does not exist" (WARN)

The Graph Analyser process runs automatically as part of the Housekeeper Moolet, to calculate Vertex Entropy for your topological nodes. The Graph Analyser process logs details of its processing to the Moogfarmd log file. Example log entries:

Starts processing for a topology named "physical":

Starting graph analysis of topology [physical]
...
Setting topology state from [OUTDATED] -> [PROCESSING] for [physical]

Processes nodes in the "physical" topology:

Performing analysis on 15023 nodes in topology [physical]

Example errors:

"Skipping topology [physical] as it has no nodes." (INFO)
"Failed to update vertex entropy values for topology [physical]" (WARN)
"Topology with name [physical] does not exist" (WARN)
"Topology [physical] state is [OUTDATED], skipping pending re-analysis" (INFO)

Completes processing:

Completed graph analysis of topology [physical], time elapsed 10s

Moogsoft Bridge uses a store and forward architecture to push events and other messages from a local RabbitMQ cluster to the Message Bus.

Moogsoft Bridge outputs logs to:

See Moogsoft Bridge for more information.