Logs
Mission Control provides centralized logging in its Control Plane. A centralized location allows querying for errors, monitoring messages, and finding root causes to issues.
Logging is configured during the installation of Mission Control.
Architecture
Mission Control aggregates, indexes, stores, and accesses logs with queries.
A Vector DaemonSet on each Kubernetes node actively scrapes the logs from the local pods.
Apache Cassandra® and DataStax Enterprise (DSE) pods monitor the logs on their pods through a Vector Sidecar.
Nodes added to racks, datacenters, and clusters are automatically discovered and scraped for logging and metric information.
Examine logs
Access these from the browser window to which you ported the services.
Mission Control collects logs that running containers produce and static log file locations and makes them available in a common location within the UI. For a cluster of up to 500 nodes and 90 days of stored logs, query responses should return within 100 ms for a query spanning the previous hour with a pod name label or value.
To examine logs in the Mission Control UI:
-
In the Home Clusters dialog, click the target cluster namespace.
-
Click the Observability tab.
-
Click the Logs tab.
-
Review log activity for your cluster.
-
Optional: To filter the results:
-
In the Search field, enter a specific node name.
-
In the Node field, select a specific node name.
-
In the Start or End fields, enter the dates for a specific time period.
-
-
Optional: Click the clipboard icon on the row of your target message to copy and locally view log details.
Types of logs
- gc
-
also known as garbage collection. Aids in memory management by listing deallocated programming objects no longer used.
- systemd
-
centralized logs of all Linux kernel and user processes system messages.
- debug
-
aids in diagnosing and fixing bugs and errors.
Query the system.log within the Mission Control UI view.
