Logs

As an administrator, you can access all logs for Meeting Management and Meeting Server.

Note: Most timestamps are in UTC. The exception is event logs which are displayed in your browser's time zone when viewed within Meeting Management.

Note: Event logs for a specific meeting are available on the Meetings page, meeting details view, for up to a week after the meeting has ended. See the User Guide for Video Operators for details. Event log information is also included in the Meeting Management system log, but you will not see the messages sorted by the meeting they belong to.

Meeting Management logs

All the Meeting Management logs including log bundle, system logs and audit logs can be accessed on the CMM logs tab.

Log bundle

From the Logs page CMM logs tab, you can download a log bundle for Meeting Management using Download log bundle button. The downloaded logs contain information that Cisco Support would need for troubleshooting:

  • The latest system and audit logs
  • Configuration details (redacted to not include passwords)
  • Version number
  • A list of crash reports

  • 90 day license report

If you need to contact Cisco Technical Support, always include the log bundle.

Note: All logs accessed on the CMM logs tab are for Meeting Management are for Meeting Management, even though many of the messages are based on information received from Meeting Server Call Bridges.

System log servers

On the System log server tab, you can add the servers to which Meeting Management should send the system logs. System logs contain all information on what has happened on Meeting Management. The latest system logs are included in the log bundle. You can configure up to 5 system log servers to track events and activity on Meeting Management.

Only the latest logs are stored locally, so we strongly recommend that you set up an external syslog server to keep the full history in case you need it for Support.

Note: When troubleshooting issues with Meeting Management, you may need to look at Meeting Server logs as well. We strongly recommend that you use external syslog servers for all instances of Meeting Management, and for all your Meeting Servers.

To configure system log servers:

  1. Click Add log server button

  2. Enter Server address and Port

  3. Select Protocol

  4. Upload certificates using Upload certificate button

  5. Click Add button to complete configuring the log server

Audit log servers

On the Audit log server tab, you can add the servers to which Meeting Management should send the audit logs. Audit logs contain information about actions performed by Meeting Management users. For example, any settings change, login details and so on.

If audit logs are required in your organization, we recommend that you set up an external syslog server for audit logs. You can configure up to 5 system log servers to track events and activity on Meeting Management.

To configure audit log servers:

  1. Click Add log server button

  2. Enter Server address and Port

  3. Select Protocol

  4. Upload certificates using Upload certificate button

  5. Click Add button to complete configuring the log server

Crash reports

The Meeting Management crash reports can be accessed on the Crash reports tab in CMM Logs page

Detailed tracing

When requested from support, you can enable detailed tracing while reproducing an issue to gather comprehensive logs.

Detailed tracing is available for:

  • Meeting Server API

  • Meeting Server CDR

  • Meeting Server Events

  • TMS API

  • Meeting Server Cloud Connector API

You can configure to trace logs for every 1 minute, 10 minutes, 30 minutes or 24 hours.

90 day license report

90 day license report provides visibility on customers' licensing usage to the support team, without having them to join a Webex meeting. The support team can then parse the 90 day license report and notify the customers of any necessary changes to the licenses.

Meeting Server logs

Meeting Management administrators can download log bundle and trace detailed logs for Meeting Server and Edge nodes using the CMS logs tab in the Logs page.

Log bundle

Meeting Management allows administrators to collect the logs for servers including Call Bridge and Edge Nodes after adding them.

The steps for collecting logs for Meeting Servers are as follows:

  1. Click Select server button

  2. Select Call Bridges or Edge Nodes from a list of servers

  3. Click Generate log bundle button to generate the logs

Note: To generate log bundle for all the nodes in a cluster, on the Select Server page while selecting the cluster node, ensure that you select each node in the cluster.

After the log bundle is generated, you can download the logs of the selected server. The generated log bundle is named logbundle_<host name>_YYYY-MM-hh-mm-ss.tar.gz. The generated logs can be downloaded within 24 hours from the CMS log bundle page.

Detailed tracing

Meeting Management allows the administrators to trace logs of different Meeting Server modules like SIP, Active Control, Active Speaker, ICE and so on.

The steps for enabling detailed tracing are as follows:

  1. Click Select server button

  2. Select Call Bridges from a list of servers to trace the detailed logs.

  3. In the Traces list, you can enable or disable tracing for different Meeting Server components.

Note: Enabling tracing debug is an overload on the selected servers. Ensure that you enable detailed tracing only when necessary.

You can also set how often you want to trace the logs. For example, you can configure to trace logs for every 10 or 60 minutes or you can set an interval of your choice in the hh:mm format.

Note: To generate log bundle for all the nodes in a cluster, on the Select Server page while selecting the cluster node, ensure that you select each node in the cluster.

Click Disable all to disable detailed tracing for all Meeting Server components.