The DevOps Center

The DevOps Center is a tool for monitoring, troubleshooting, and incident investigation. It consists of an interactive log viewer, providing views into this Fusion cluster’s hosts and services using metrics and events.

  • Metrics come from the system_monitor collection.

    See System Metrics for details about this collection.

  • Events come from the system_logs collection.

You can export all metrics and events for any selected time period.

In any Fusion app, you can open the DevOps Center by navigating to System > DevOps Center:

Navigating to the DevOps Center

System requirements

The DevOps Center is included as part of Fusion Server 4.2 and above. It requires the following:

  • Your Web browser must support HTML5.

  • Every node that you want to monitor must be running Fusion Server version 4.2.0 or later.

  • Every node that you want to monitor must be running the agent and log-shipper services.

The DevOps Center is enabled by Fusion’s default configuration.

The Log Viewer

The Log Viewer displays service logs and request logs from Fusion’s system_logs collection.

DevOps Log Viewer dashboard

By default, timestamps are displayed in local time, as determined by your browser. To view timestamps in UTC (unless default.timezone is set to another time zone in fusion.cors), set LOCAL TIMEZONE to "Off".

Auto-Refesh is off by default, to display static log data. To display real-time logs, set this to "On".

See Export Data from the DevOps Center to learn how to export log data.

Service logs

Service log files are written to the filesystem by each running service, such as var/log/api/api.log, var/log/proxy/proxy.log, and so on. Fusion indexes them in the system_logs collection with type=java.

In the DevOps Center, you can filter service logs by:

  • Service

  • Log level

  • Host

Request logs

HTTP request log files are written to the filesystem by Jetty, at var/log/proxy/jetty_request_<date>.log. Fusion indexes them in the system_logs collection with type=http.

In the DevOps Center, you can filter request logs by:

  • HTTP status code

  • HTTP method

  • Host

Audit logs

Audit logs provide you with a resource for tracking actions within Fusion, including the date, time, user responsible, and more. Example use cases include determining:

  • When a query profile’s configuration changed to use bq instead of boost

  • Who created a datasource configuration and why they did so in a particular way

  • Whether a deployment is being tampered with

In the DevOps Center, you can filter audit logs by:

  • Status

  • Action

  • Verb

For example, you can examine the audit logs to learn who deleted a query pipeline by faceting by the approximate date range and selecting the Verb facet DELETE.

Audit logs deleted pipeline

Click the Export audit logs for detailed log data, including:

Field Data

mdc_action_s

ACCESS

mdc_request_method_s

DELETE

mdc_request_uri_s

https://fusion-cluster:6764/api/apps/documentation/query-pipelines/cyber-monday

mdc_user_agent_s

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:81.0) Gecko/20100101 Firefox/81.0

mdc_username_s

johnDoe

timestamp_tdt

["2020-10-19T16:23:03.041Z"]