All
0 Results filtered by:
We couldn't find any results
You can search all listings, or try a different spelling or keyword. Still nothing? Dynatrace makes it easy to create custom apps.
OpenShift Control PlaneOpenShift Control Plane
Get insights into your OpenShift control plane with metrics from its components.
Extension- Product information
- Release notes
Overview
This is an extension for monitoring the OpenShift control plane. It comes with an out-of-the-box dashboard and pre-configured alerts for easiness of use. It requires metrics already ingested into Dynatrace via Prometheus integration. Follow the steps in the setup section for proper setup of this extension.
Use cases
- Alert on control plane components not being ready.
- Inspect the control plane using out-of-the-box dashboards.
- Create custom dashboards and alerts using metrics exposed by components of the control plane.
Compatibility information
- OpenShift 3 or OpenShift 4 (self-managed)
- Cluster version 1.252+ is required
- AG version 1.249+ running within the Kubernetes cluster. To have an ActiveGate in your Kubernetes cluster, deploy Dynatrace using Dynatrace Operator (recommended) or deploy an ActiveGate as a StatefulSet.
Setup
Install extension
Follow the steps to install the OpenShift control plane extension.
1. Enable Prometheus monitoring in Dynatrace
In your Dynatrace environment, go to Kubernetes, edit your Kubernetes cluster settings, and turn on Enable monitoring and Monitor annotated Prometheus exporters. For more information see our official documentation.
2. Start ingesting control plane metrics
To ingest metrics exposed by the OpenShift control plane, the related services need to be annotated with specific Dynatrace annotations. Based on the used OpenShift version, the YAML files referenced in the commands below define a default set of annotations, enabling the ingestion of all metrics used by the OpenShift control plane extension. Before executing any of the instructions below, ensure your kubectl is configured to use the Kubernetes cluster you want to monitor. If the default set of annotations fits your needs, use the corresponding instructions below. Otherwise, download the files first and adapt them accordingly.
OpenShift 4
kubectl apply -f https://raw.githubusercontent.com/dynatrace-extensions/kubernetes-control-plane/main/scripts/control-plane-monitoring-annotations-ocp4.yaml
OpenShift 3
kubectl apply -f https://raw.githubusercontent.com/dynatrace-extensions/kubernetes-control-plane/main/scripts/control-plane-monitoring-annotations-ocp3.yaml
Verification and troubleshooting
After some minutes, you can verify if everything works as expected by finding control plane related metrics using Dynatrace metrics browser. kube_pod_status_ready is one of the metrics to search for.
For troubleshooting and further annotation methods, see Monitor Prometheus metrics in Dynatrace documentation.
3. Add extension to environment
To add this extension to your environment click Add to environment on the page of this extension in the Dynatrace Hub. After activating the extension, select Dashboards in Dynatrace. You should now find an out-of-the-box OpenShift control plane dashboard.
4. Activate metric events for alerting
Additionally, the extension comes with multiple pre-configured metric events for alerting. To activate them:
-
From the Dynatrace navigation menu, select Settings > Anomaly detection > Metric events.
-
Find the following events
- OpenShift control plane: cluster not ready: notifies you if the cluster is not ready (based on the readyz API health endpoint).
- OpenShift control plane: etcd pod not ready: notifies you if any etcd pod is not ready.
- OpenShift control plane: API server pod not ready: notifies you if any API server pod is not ready.
- OpenShift 4 specific events:
- OpenShift control plane: low number of master nodes: notifies you if the number of master nodes is below a specified threshold.
- OpenShift control plane: DNS pod not ready: notifies you if any DNS pod is not ready.
- OpenShift control plane: scheduler pod not ready: notifies you if any scheduler pod is not ready.
- OpenShift control plane: controller manager pod not ready: notifies you if any controller manager pod is not ready.
- OpenShift 3 specific events:
- OpenShift control plane: low number of master nodes: notifies you if the number of master nodes is below a specified threshold.
- OpenShift control plane: controller pod not ready: notifies you if any controller pod is not ready.
-
If necessary, select the Edit button to customize the event conditions.
-
Move the switch next an event to the On position to activate it.
Uninstall the extension
1. Stop metric ingest
As metric ingest might be subject to additional costs (see licensing), it can be stopped by removing the annotations from the related services. If you followed the instructions described in the "Start ingesting control plane metrics" section, you can use kubectl to remove the annotations, by referencing the previously applied file in a kubectl delete -f command, as shown below for the default YAML files. Before executing any of the instructions below, ensure your kubectl is configured to use the right Kubernetes cluster.
OpenShift 4
kubectl delete -f https://raw.githubusercontent.com/dynatrace-extensions/kubernetes-control-plane/main/scripts/control-plane-monitoring-annotations-ocp4.yaml
OpenShift 3
kubectl delete -f https://raw.githubusercontent.com/dynatrace-extensions/kubernetes-control-plane/main/scripts/control-plane-monitoring-annotations-ocp3.yaml
2. Deactivate the extension
To remove the out-of-the-box dashboard and alerts, deactivate the extension via the Dynatrace Hub.
Extension content
Content typeNumber of items included
metric metadata
5
dashboards
1
metric query
5
alerts
9
Customer story KeyBank
“Dynatrace gives us deep visibility into our container-based applications running on Red Hat OpenShift which helps us proactively identify performance and application issues before they impact users.”
John Rzeszotarski
Director of Continuous Delivery and Feedback
Related to OpenShift Control Plane
Full version history
To have more information on how to install the downloaded package, please follow the instructions on this page.
ReleaseDate
Full version history
No release notes
Full version history
- Use "builtin:kubernetes.cluster.readyz" metric for Cluster readiness status tile
- Improve visualization of Cluster readiness status tile
Full version history
- allow filtering by Kubernetes cluster on included dashboard
Full version history
first public release