---
title: OCI Cache
description: >-
  OCI Cache is a fully managed, Redis-compatible caching service for high-speed,
  low-latency data access.
breadcrumbs: Docs > Integrations > OCI Cache
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# OCI Cache
Integration version1.0.0
{% callout %}
# Important note for users on the following Datadog sites: us2.ddog-gov.com

{% alert level="info" %}
To find out if this integration is available in your organization, see your [Datadog Integrations](https://app.datadoghq.com/integrations) page or ask your organization administrator.

To initiate an exception request to enable this integration for your organization, email [support@ddog-gov.com](mailto:support@ddog-gov.com).
{% /alert %}

{% /callout %}

## Overview{% #overview %}

OCI Cache is a fully managed, Redis-compatible in-memory caching service. This integration lets you monitor cache CPU and memory utilization, network throughput, client connections, and keyspace hit rates by collecting metrics and tags from the [`oci_redis`](https://docs.oracle.com/iaas/Content/ocicache/metrics.htm) namespace.

## Setup{% #setup %}

### Installation{% #installation %}

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

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

### Metrics{% #metrics %}

|  |
|  |
| **oci.redis.cpu_utilization**(gauge)         | Percentage of time the CPU is busy, out of total busy and idle time.*Shown as percent*                                                                                  |
| **oci.redis.memory_utilization**(gauge)      | Amount of available memory in use, measured by pages. Expressed as a percentage of used pages compared to unused pages.*Shown as percent*                               |
| **oci.redis.network_bytes_in**(gauge)       | Bytes received per second.*Shown as byte*                                                                                                                               |
| **oci.redis.network_bytes_out**(gauge)      | Bytes transmitted per second.*Shown as byte*                                                                                                                            |
| **oci.redis.used_memory**(gauge)             | Total bytes allocated for all purposes, including dataset, buffers, and other uses.*Shown as byte*                                                                      |
| **oci.redis.keyspace_hits**(count)           | Number of successful read-only key lookups in the main dictionary.*Shown as hit*                                                                                        |
| **oci.redis.connected_clients**(gauge)       | Number of client connections, excluding read replica connections.*Shown as connection*                                                                                  |
| **oci.redis.evicted_keys**(count)            | Number of keys evicted because the memory limit was reached.*Shown as key*                                                                                              |
| **oci.redis.replication_lag**(gauge)         | Time a read replica lags behind the primary node when applying changes. Applies to read replicas only.*Shown as second*                                                 |
| **oci.redis.keyspace_misses**(count)         | Number of unsuccessful read-only key lookups in the main dictionary.*Shown as miss*                                                                                     |
| **oci.redis.primary_replica_offset**(gauge) | Bytes the primary node is sending to all replicas, representing the write load on the replication group. Applies to nodes in a replicated configuration.*Shown as byte* |
| **oci.redis.expired_keys**(count)            | Total number of key expiration events.*Shown as key*                                                                                                                    |

### Service Checks{% #service-checks %}

OCI Cache does not include any service checks.

### Logs{% #logs %}

OCI Cache logs, including audit logs and service logs, are collected through the [Oracle Cloud Infrastructure](https://docs.datadoghq.com/integrations/oracle_cloud_infrastructure.md) integration and the OCI Service Connector Hub. Log collection is configured and toggled from the [OCI integration tile](https://app.datadoghq.com/integrations/oracle-cloud-infrastructure).

### Events{% #events %}

OCI Cache does not include any events.

## Troubleshooting{% #troubleshooting %}

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