Contact Free trial Login

Viewing Log Data

CloudHub provides access to log data that includes deployment messages and events for each worker.

Logs and diagnostics are currently available only for applications deployed to CloudHub workers. In cases when applications are deployed to a local server, you can send data to external analytics software.

Applications deployed to Pivotal Cloud Foundry (PCF) don’t expose any log data through Runtime Manager, but you can see event logs on Pivotal’s UI.

View Logs

View logs for applications deployed to CloudHub.

  1. In Runtime Manager, click Applications in the left menu, and then click the application that is deployed to CloudHub to open the management panel on the right.

  2. Click Logs.

    The application logs are displayed.

  3. The Deployments section on the right of the logging screen lets you selectively view the output by day, deployment, system log, and workers. You can unapply a filter by unticking the checkbox next to a date.

    ELMfilters

Download Logs

Each worker in each CloudHub deployment has separate logs you can download.

  1. In the Deployment filters section on the right, find the date and worker you want to view.

  2. Click the download icon next to the worker, and select Logs.

DownloadLogs

The log file is a text file with the file extension .log in the format <deployment-ID>-<instance-ID>.log. You can view the log file with a text editor.

To archive or download CloudHub application logs for audit, analytics, or other purposes at regular intervals, use the Custom Log Appender to extract logs.

Download Diagnostics

Diagnostics display the Java thread dump of each CloudHub worker in each deployment. These indicate the current state of the server, which is useful for debugging and support.

For apps that run on a Mule versions earlier than 3.8.0 (excluding version 3.7.4), diagnostics are not available.
  1. In the Deployment filters section on the right, select the date and worker for which you want to download diagnostics.

  2. Click the download icon next to it, and select Diagnostics.

The downloaded log file is a text file with the .txt file extension and named in the format of <app-name>-instance-<instance-ID>-<worker-number>-diag.txt. You can view this file with a text editor.

In diagnostics, the instance ID of a worker is the deployment ID plus the worker number (0 to 4).

You can also use the following URL to download a diagnostics file directly:

api/v2/applications/appName/instances/instanceId/diagnostics

About Log Persistence

CloudHub stores logs of up to 100 MB per application per worker, or for up to 30 days, whichever limit is reached first.

About Log Timezones

CloudHub stores log data in Universal Time (UTC); however, the console displays the log using your computer’s local time zone.

Search Logs

Search for logs that contain specified values, or use advanced search to search for logs by date and priority.

  1. Enter a value in the search box, or click Advanced to search for logs for a specified time, day, date range, and message priority.

  2. Click Apply.

    ELMAdvancedSearch

Search by Date and Time

The Date & Time filter lets you search the log by specifying a date range. Possible values are:

  • Last hour

  • Last 24 hours

  • Last week

  • Last month

Search by Message Priority

The Priority filter lets you view specific events in the log. You can also specify different priorities by typing priority<type> in the search box, as shown in the Command column in the table.

Possible values are:

Value Description Command

All Priorities

List all messages

N/A

ERROR

List only error messages, such when an exception occurs.

priority:ERROR

FATAL

List only fatal messages for when an application fails

priority:FATAL

INFO

List informative messages

priority:INFO

SYSTEM

List messages about application and worker startup

priority:SYSTEM

CONSOLE

List message about console events such as setting the objectstore

priority:CONSOLE

WARN

List warning messages

priority:WARN

DEBUG

List debugging messages

priority:DEBUG

Wildcard Searching

You can filter log data by entering search terms into the search box at the top of the log page that match results in the log message. You can also search for an exact term in the log message with a few common quantifiers for wildcard searching:

  • ? - The question mark matches zero or one of the preceding elements.

  • - The asterisk matches zero or more of the preceding elements.