CliQr is now part of Cisco Learn More About Cisco

Log File Location

Types of Log Files

The CloudCenter platform generates log files for each major component  to help troubleshoot problems and error. CloudCenter log files are generated through the log4J library and follows the log4j format.

 

ComponentLog FileLocationDescription
CCOosmosix.log

/usr/local/tomcat/logs/osmosix.log

The logs generated by the CCO application.

Icon

CloudCenter maintains 10 revisions of these log files. Be sure the send the latest log file version.

CCMosmosix.log/usr/local/tomcat/logs/osmosix.log

The logs generated by the CCM application.

Icon

CloudCenter maintains 10 revisions of these logs. Be sure the send the latest log file version.

AMQP
  • amqp.log
  • startup_log
/var/log/rabbitmq

The logs generated by the AMQP server. CloudCenter uses RabbitMQ as the open source message broker to implement AMQP

Linux Application VMcliqr-agent.log

/usr/local/c3agent/jetty/logs/cliqr-agent.log

The logs generated by the management agent application.

service.log

 /usr/local/osmosix/logs/service.log 

The logs generated for application VMs with mid-tier services like Tomcat, Apache, and so forth. If those services are present, CloudCenter generates a separate log file with messages specific to the orchestration of that service.
Windows Application VMnode-metadata.logC:\opt\jetty\logs

The logs generated for the node metadata.

cliqr-agent.logC:\opt\jetty\logs

The logs generated by the management agent application.

service.logC:\Program Files\osmosix\logsThe logs generated for application VMs with mid-tier services like Tomcat, Apache, and so forth. If those services are present, CloudCenter generates a separate log file with messages specific to the orchestration of that service.

Environment Variables for Callout Scripts

timestamp is the file name/usr/local/osmosix/callout/<module_name>/logs/<timestamp>

A full list on input variables is available in the callout script log.

 

Logging Levels

For detailed logging, CloudCenter offers multiple levels to control the granularity of information printed in the log files. CloudCenter provides standard logging levels. Out-of-the box the logging level is set to default.

level
  • Description: The log level for this file.
  • Type: Enumeration

    EnumerationDescription
    ALLAll levels of logging
    DEBUGDetailed information on the system flow and are generally written to logs.
    ERROROther runtime errors or unexpected conditions and are generally visible on the CCM UI.
    FATALSevere errors that cause premature termination and are generally visible on th CCM UI.
    INFOStartup or shut down runtime events and are are generally visible on the CCM UI.
    so be conservative and keep to a minimum.
    TRACEDetailed log information and are generally written to logs.
    WARNUse of deprecated APIs, poor use of API, other runtime situations that are undesirable or unexpected and area generally visible on the CCM UI
     TRACE_INT Detailed log information and are generally written to logs.
    OFFTurns off logging.

Retrieve a Log File

To retrieve any log file, follow this procedure:

  1. Change to the required log file directory. For example, if you are retrieving the CCO log file:
    cd /usr/local/tomcat/logs
  2. Download the log file.
  3. If you are forwarding this log file to CloudCenter Support, attach this file to your support ticket.

The ELK Stack

See Download Log File

  • No labels