Feature request / Enhancement(OCI Cache / Redis)

[thallesdaniell]

📌 Feature request: support for oci_redis namespace (OCI Cache / Redis)

Summary

The oracle‑cloud‑integration stack does not forward metrics from OCI Cache (Redis).
Oracle Monitoring exposes them under the namespace oci_redis, but the default Service Connector created by the stack ignores that namespace, so no Redis data reaches Datadog.

Current behaviour

• Tested stack: datadog‑oci‑orm v1.4.4 (released 30 Apr 2025)
• Namespaces like oci_compute and oci_apm work fine.
• Metrics matching oci_redis.* never show up in Metrics Explorer or the API.

Desired behaviour

• Add oci_redis to the namespace allow‑list consumed by the Service Connector.
• Export every metric in the official docs: hits/misses, ops‑per‑sec, memory, replication lag, etc.
• Re‑use the existing IAM policy pattern (read‑only on Monitoring).

Why this matters

Critical workloads rely on OCI Cache with Redis for caching and queueing. Without these metrics:

• We can’t alert on latency spikes, memory pressure, or replication issues.
• Dashboards are incomplete, impacting SLO tracking.

Steps to reproduce

1. Deploy datadog‑oci‑orm v1.4.4 in tenancy XYZ.
2. Spin up a managed Redis cluster, generate traffic.
3. In Metrics Explorer, search for oci_redis.* → no results.

Impact

• Full visibility into managed Redis performance.
• Ability to set alerts for memory saturation, replication lag, latency, etc.
• Consistency with other Datadog integrations (AWS ElastiCache, Azure Cache, GCP Memorystore).

Extra info

• I can attach the terraform plan/tfvars for the stack and the output of
  oci monitoring metric-data summarize-metrics-data --namespace oci_redis ...
• Happy to beta‑test any PR or experimental branch in prod.

Thanks for the great work on the OCI connector! 🙌