---
title: Oracle Container Engine for Kubernetes
description: OKE is an OCI managed container orchestration service.
breadcrumbs: Docs > Integrations > Oracle Container Engine for Kubernetes
---

# Oracle Container Engine for Kubernetes
Supported OS Integration version1.0.0
## Overview{% #overview %}

Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) is a managed Kubernetes service that simplifies the operations of enterprise-grade Kubernetes at scale.

This integration collects metrics and tags from the [`oci_oke`](https://docs.oracle.com/en-us/iaas/Content/ContEng/Reference/contengmetrics.htm) namespace to help you monitor your Kubernetes control plane, clusters, and node states.

Deploying the [Datadog Agent](https://docs.datadoghq.com/agent/kubernetes.md#installation) on your OKE cluster can also help you track the load on your clusters, pods, and individual nodes to get better insights into how to provision and deploy your resources.

In addition to monitoring your nodes, pods, and containers, the Agent can also collect and report metrics from the services running in your cluster, so that you can:

- Explore your OKE clusters with [pre-configured Kubernetes dashboards](https://app.datadoghq.com/dashboard/lists/preset/3?q=kubernetes)
- Monitor containers and processes in real time
- Automatically track and monitor containerized services

## Setup{% #setup %}

Once you set up the [Oracle Cloud Infrastructure](https://docs.datadoghq.com/integrations/oracle_cloud_infrastructure.md) integration, ensure that the `oci_oke` namespace is included in your [Connector Hub](https://cloud.oracle.com/connector-hub/service-connectors).

Because Datadog already integrates with Kubernetes, it is ready-made to monitor OKE. If you're running the Agent in a Kubernetes cluster and plan to migrate to OKE, you can continue monitoring your cluster with Datadog.

Deploying the Agent as a DaemonSet with the [Helm chart](https://docs.datadoghq.com/agent/kubernetes.md?tab=helm) is the most straightforward (and recommended) method, since it ensures that the Agent will run as a pod on every node within your cluster and that each new node automatically has the Agent installed. You can also configure the Agent to collect process data, traces, and logs by adding a few extra lines to a Helm values file. Additionally, OKE node pools are supported.

## Data Collected{% #data-collected %}

### Metrics{% #metrics %}

|  |
|  |
| **oci.oke.apiserver\_request\_count**(count)   | Number of requests received by the Kubernetes API Server.*Shown as request*                                                                           |
| **oci.oke.apiserver\_response\_count**(count)  | Number of different non-200 responses (that is, error responses) sent from the Kubernetes API server.*Shown as response*                              |
| **oci.oke.kubernetes\_node\_condition**(gauge) | Number of worker nodes in different conditions, as indicated by the Kubernetes API server.*Shown as node*                                             |
| **oci.oke.node\_state**(gauge)                 | Number of compute nodes in different states.*Shown as node*                                                                                           |
| **oci.oke.unschedulable\_pods**(gauge)         | Number of pods that the Kubernetes scheduler is unable to schedule. Not available in clusters running versions of Kubernetes prior to version 1.15.x. |

## Troubleshooting{% #troubleshooting %}

Need help? Contact [Datadog support](https://docs.datadoghq.com/help/).

## Further Reading{% #further-reading %}

- [How to monitor Oracle's Kubernetes Engine with Datadog](https://www.datadoghq.com/blog/monitor-oracle-kubernetes-engine/)