Monitoring OpenShift
- Supported Versions
- Installing the Instana agent in OpenShift
- Instana AutoTrace webhook
- Accessing OpenShift Information
- Metrics collection
- Troubleshooting
Supported Versions
Instana supports OpenShift according to the Red Hat OpenShift support policies. OpenShift platform versions in Full Support and Maintenance Support are also supported by Instana. The same maintenance support end dates apply for Instana's OpenShift support.
Installing the Instana agent in OpenShift
The Agent Setup Quick Start for OpenShift describes how to install the Instana agent into your cluster in a production-ready configuration.
Instana AutoTrace webhook
The Instana AutoTrace webhook is an admission controller mutating webhook that automatically configures the Instana tracing on Node.js, .NET Core and Ruby applications running across the entire OpenShift cluster.
Usage of Instana AutoTrace webhook is very much advised if you run Node.js, .NET Core or Ruby applications on your OpenShift 4.5+ clusters.
Accessing OpenShift Information
See Kubernetes for more details.
Metrics collection
To view the metrics, select Infrastructure in the sidebar of the Instana User interface, click a specific monitored host, and then you can see a host dashboard with all the collected metrics and monitored processes.
Once the agent has been deployed to your cluster, the sensor will report detailed data about the cluster and the resources deployed into it. Instana will collect general Kubernetes information. See Kubernetes for more information. In addition we also collect information about DeploymentConfigs which are specific to OpenShift clusters.
DeploymentConfigs
| Field | Description |
|---|---|
| Conditions | Type, Status, Timestamp, Reason, Message |
| Labels | Key/value pairs |
| CPU Requests | Aggregated CPU requests of all running containers of this DeploymentConfig |
| CPU Limits | Aggregated CPU limits of all running containers of this DeploymentConfig |
| Memory Requests | Aggregated memory requests of all running containers of this DeploymentConfig |
| Memory Limits | Aggregated memory limits of all running containers of this DeploymentConfig |
| Pods Requested | Available / Desired Pods |
| Pods Statuses | Pending / Unscheduled / Unready Pods |
| Pending phase duration | In most cases can be interpreted as rollout duration |
Within the OpenShift panel, we provide an overview of DeploymentConfigs:
DeploymentConfig dashboard:
Health signatures
For each sensor, there is a curated knowledgebase of health signatures that are evaluated continuously against the incoming metrics and are used to raise issues or incidents depending on user impact.
Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of any given entity.
For information about the built-in event for the OpenShift sensor, see the Built-in events reference.
Troubleshooting
See Kubernetes for more details.