Oracle Cloud Infrastructure

Documentos > Integraciones > Oracle Cloud Infrastructure

Información general

Oracle Cloud Infrastructure (OCI) es una infraestructura como servicio (IaaS) y plataforma como servicio (PaaS) utilizada por empresas. Con un completo conjunto de servicios gestionados para alojamiento, almacenamiento, redes, bases de datos y mucho más.

Utiliza la integración de OCI de Datadog para reenviar tus logs y métricas a Datadog, donde pueden servir para dashboards, pueden ayudar a solucionar problemas y ser monitorizados para la seguridad y la postura de cumplimiento.

Configuración

Recopilación de métricas

Para enviar tus métricas de OCI a Datadog:

Usa una stack de Oracle Resource Manager para crear un usuario de autenticación de Datadog, un grupo y las políticas necesarias en la región de origen de tu tenencia. Esta stack:
- Permite que el usuario de autenticación de Datadog lea datos de tus recursos de OCI.
- Permite el reenvío de métricas.
Ingresa información de tenencia en el cuadro de integración de Datadog.
Usa la stack de Oracle Resource Manager a fin de crear la infraestructura de OCI necesaria para cada región de tenencia desde la que quieres reenviar métricas.

Generar stacks de OCI e información de tenencia

Nota: Tu cuenta de usuario de OCI necesita el rol de Cloud Administrator (Administrador de la nube) para completar estos pasos.

Esta integración usa un centro de conectores de OCI, una aplicación de funciones y una infraestructura de red segura para enviar métricas de OCI a Datadog.

Un diagrama de los recursos de OCI mencionados en esta página y que muestra el flujo de los datos

Para la configuración más sencilla, Datadog recomienda crear todos los recursos de OCI necesarios con los stacks tecnológicos de ORM que se proporcionan a continuación. Como alternativa, puedes utilizar tu infraestructura de red de OCI o aplicación de función existente que cumpla los requisitos descritos en la sección Crear un stack tecnológico de reenvío de métricas.

Nota: Debes gestionar quién tiene acceso a los archivos de estado de Terraform de las stacks del gestor de recursos. Consulta la sección Archivos de estado de Terraform de la página Seguridad del gestor de recursos para obtener más información.

Crear un stack tecnológico de políticas

Un diagrama de los recursos y flujo de trabajo de OCI utilizado para la autenticación de integración

Se debe crear una stack de políticas de ORM en la región de origen de la tenencia. La stack de políticas crea:

Un grupo dinámico con resource.type = 'serviceconnectors', para permitir el acceso al centro de conectores.
Un usuario llamado DatadogAuthUser, que Datadog usa para leer recursos de tenencia.
Un grupo al que se añade el usuario creado para acceder a la política.
Una política en el compartimento raíz para permitir que los centros de conectores lean métricas e invoquen funciones. Además, otorga al grupo de usuarios creado acceso de lectura a los recursos de la tenencia. Se añaden las siguientes instrucciones a la política:

Allow dynamic-group <GROUP_NAME> to read metrics in tenancy
Allow dynamic-group <GROUP_NAME> to use fn-function in tenancy
Allow dynamic-group <GROUP_NAME> to use fn-invocation in tenancy
Allow group <DOMAIN>/<USER_GROUP_NAME> to read all-resources in tenancy

Para crear la stack, tu cuenta de usuario debe poder crear políticas y grupos dinámicos.

Haz clic en el botón Create a stack (Crear un stack tecnológico) del cuadro de integración de Datadog y OCI.
Acepta las Condiciones de uso de Oracle.
En el desplegable Working directory (Directorio de trabajo), selecciona datadog-oci-orm/policy-setup.
Deja la opción de utilizar proveedores de Terraform personalizados desmarcada.
Proporciona un nombre descriptivo como datadog-metrics-policy-setup y selecciona el compartimento en el que deseas desplegarlo.
Haz clic en Next (Siguiente).
Asigna un nombre al grupo dinámico, el grupo de usuarios y a la política que se van a crear, o usa los nombres predeterminados proporcionados.
Proporciona el nombre del dominio del usuario que ejecuta la stack. El nombre de dominio predeterminado es Default.
Asegúrate de que se encuentre seleccionada la región de origen de la tenencia.
Haz clic en Next (Siguiente).
Haz clic en Create (Crear).

Notas:

Si el usuario que ejecuta la stack pertenece a un dominio de IAM diferente al de Default, proporciona ese nombre de dominio para que el usuario de autenticación, el grupo dinámico y el grupo de usuarios solo se creen en ese dominio.
Si el usuario y el grupo no se crean en el dominio predeterminado, asegúrate de que el dominio se replique en todas las regiones suscritas de la tenencia. Consulta Replicación de un dominio de identidad en varias regiones para obtener más información.

Introducir datos de tenencia

Ingresa el OCID y la región de origen de la tenencia que quieres monitorizar en el cuadro de integración de Datadog y OCI.
- Puedes encontrar esta información en la página de detalles de la tenencia.
- Ingresa la región de origen con el valor Region Identifier (Identificador de región) de la página Regiones y dominios de disponibilidad de OCI.
Para el DatadogAuthUser creado después de ejecutar la stack anterior, copia el valor OCID del usuario y pégalo en el campo User OCID (OCID del usuario) en el cuadro de integración de Datadog y OCI.
Volviendo a la consola de OCI, genera una API key (Clave de API) con estos pasos:
a. Vuelve a la página DatadogAuthUser que se creó.
b. En la esquina inferior izquierda de la pantalla, en Resources (Recursos), haz clic en API keys (Claves de API).
c. Haz clic en Add API key (Añadir clave de API).
d. Haz clic en Download private key (Descargar clave privada). e. Haz clic en Add (Añadir).
f. Aparece una ventana emergente Configuration file preview (Vista previa del archivo de configuración), pero no es necesario realizar ninguna acción; cierra la ventana emergente.

La página Añadir clave de API en la consola de OCI

Copia el valor Fingerprint (Huella dactilar) y pégalo en el campo Fingerprint (Huella dactilar) del cuadro de integración de Datadog y OCI.
Copia el valor de la private key (clave privada) con estos pasos:
a. Abre el archivo de clave privada .pem descargado en un editor de texto, o utiliza un comando de terminal como cat para mostrar el contenido del archivo.
b. Copia todo el contenido, incluidos -----BEGIN PRIVATE KEY----- y -----END PRIVATE KEY-----.
Pega el valor de la clave privada en el campo Private Key (Clave privada) del cuadro de integración de Datadog y OCI.

Crear una stack de reenvío de métricas

Todos los recursos que crea esta stack se despliegan en el compartimento especificado. Asegúrate de que el usuario que ejecuta esta stack tenga acceso para crear recursos en el compartimento.

Ve a Create stack (Crear stack) en la consola de OCI.
Acepta las Condiciones de uso de Oracle.
En el desplegable Working directory (Directorio de trabajo), selecciona datadog-oci-orm/metrics-setup.
Deja la opción de utilizar proveedores de Terraform personalizados desmarcada.
Asigna un nombre al stack tecnológico y selecciona el compartimento en el que se desplegará.
Haz clic en Next (Siguiente).
Deja los valores de Tenancy (Tenencia) sin modificar, ya que vienen especificados por tu región e inquilino actuales, así como por el compartimento seleccionado anteriormente.
En el campo Datadog API Key (Clave de API de Datadog), ingresa tu clave de API de Datadog.
En el campo Datadog Environment Endpoint (Endpoint del entorno de Datadog), selecciona el endpoint que coincida con tu sitio de Datadog:

Sitio de Datadog	Endpoint
US1	ocimetrics-intake.datadoghq.com
US3	ocimetrics-intake.us3.datadoghq.com
US5	ocimetrics-intake.us5.datadoghq.com
EU1	ocimetrics-intake.datadoghq.eu
AP1	ocimetrics-intake.ap1.datadoghq.com

Nota: La integración de OCI no es compatible con el sitio US1-FED.

En la sección Network options (Opciones de red), deja marcada la opción Create VCN. a. En el campo vcnCompartment, selecciona tu compartimento.

Si utiliza un VCN existente, debe proporcionar el OCID de la subred a la pila. Asegúrese de que el VCN:

Se permite realizar llamadas de salida HTTP a través de la gateway NAT.
Es capaz de extraer imágenes del registro de contenedores de OCI mediante la gateway de servicio.
Tiene las reglas de la tabla de enrutamiento para permitir la gateway NAT y la gateway de servicio.
Tiene las reglas de seguridad para enviar solicitudes HTTP.

En la sección Network options (Opciones de red), desmarca la opción Create VCN e introduce la información de tu VCN: a. En el campo vcnCompartment, selecciona tu compartimento.
b. En la sección existingVcn, selecciona tu VCN existente.
c. En la sección Function Subnet OCID (OCID de subred de función), introduce el OCID de la subred que se va a utilizar.

La pila ORM crea un repositorio función Contenedor para la región en la tenencia, y la imagen Docker se empuja a él para ser utilizado por el función.

Completa los siguientes pasos en la sección Function settings (Configuración de la función): a. En el campo Function Application shape (Forma de la aplicación de función), deja el valor como GENERIC_ARM. b. Proporciona un nombre de usuario y una contraseña para el registro de OCI Docker.
- En el campo OCI Docker registry user name (Nombre de usuario del registro de OCI Docker), indica tu nombre de usuario de OCI.
- En el campo OCI Docker registry password (Contraseña de registro de OCI Docker), proporciona un token de autorización para tu usuario de OCI. Consulta Cómo obtener un autentificador para más información.
Nota: Para verificar si el inicio de sesión en el registro de Docker es correcto, consulta Iniciar sesión en Oracle Cloud Infrastructure Registry.

Si se utiliza una aplicación de función existente, la imagen ya debe existir y se debe proporcionar la ruta completa de la imagen. A continuación, se muestra un ejemplo de ruta de imagen completa:

<REGION_KEY>.ocir.io/<TENANCY_NAMESPACE>/datadog-functions/datadog-function-metrics:latest

En <REGION_KEY>, utiliza el valor Region key (Clave de región) de la página Regiones y dominios de disponibilidad de OCI. Por ejemplo, la clave de región para US-EAST es IAD.
En <TENANCY_NAMESPACE>, utiliza el valor del Object storage namespace (Espacio de nombre de almacenamiento de objetos** en la Página de detalles de la tenencia.

Completa los siguientes pasos en la sección Function settings (Configuración de la función): a. En el campo Function Application shape (Forma de la aplicación de función), deja el valor como GENERIC_ARM. b. En el campo Function Image Path (Ruta de la imagen de la función), ingresa la ruta completa de la imagen.

Establece el Service Connector hub batch size (Tamaño de lote del centro de conectores del servicio) en 5000.
Haz clic en Next (Siguiente).
Haz clic en Create (Crear).
Vuelve al cuadro de integración de Datadog y OCI y haz clic en Create configuration (Crear configuración).

Nota: De forma predeterminada, solo se selecciona el compartimento raíz y se activan todos los espacios de nombres de métrica compatibles con la integración de Datadog y OCI (se admiten hasta 50 espacios de nombres por hub de conectores).

De manera opcional, para añadir compartimentos o editar la lista de los espacios de nombres de métrica habilitados, haz clic en Edit (Editar) en el centro de conectores recién creado.
- Haz clic en + Another compartment (+ otro compartimento) para añadir compartimentos.
- En la sección Configure source (Configurar origen), añade o elimina espacios de nombres del menú desplegable Namespaces (Espacios de nombres).

Validación

Consulta las métricas de oci.* en el dashboard de información general de la integración de OCI o en la página del explorador de métricas en Datadog.

Las métricas de la función de OCI (espacio de nombres oci.faas) y las métricas de la instancia del contenedor (espacio de nombres oci_computecontainerinstance) se encuentran en versión preliminar.

Espacios de nombre de métrica

Integración	Espacio de nombre de métrica
Base de datos autónoma	oci_autonomous_database
Block Storage	oci_blockstore
Computación	oci_computeagent, rdma_infrastructure_health, gpu_infrastructure_health, oci_compute_infrastructure_health
Instancias de contenedor (versión preliminar)	oci_computecontainerinstance
Base de datos	oci_database, oci_database_cluster
Gateway de enrutamiento dinámico	oci_dynamic_routing_gateway
FastConnect	oci_fastconnect
File Storage	oci_filestorage
Funciones (versión preliminar)	oci_faas
HeatWave MySQL	oci_mysql_database
Motor de Kubernetes	oci_oke
Equilibrador de carga	oci_lbaas, oci_nlb
Gateway NAT	oci_nat_gateway
Object Storage	oci_objectstorage
Cola	oci_queue
Hub de conectores de servicio	oci_service_connector_hub
Gateway de servicio	oci_service_gateway
VCN	oci_vcn
VPN	oci_vpn
Firewall de aplicaciones web	oci_waf

Recopilación de logs

Envía logs desde tu infraestructura en la nube de Oracle a Datadog siguiendo alguno de estos procesos:

Configura un log de OCI.
Crea una función de OCI.
Configura un conector de servicio de OCI.

Las siguientes instrucciones utilizan el portal de OCI para configurar la integración.

Registro de OCI

En el portal de OCI, navega hasta Logging -> Log Groups (Registro > Grupos de logs).
Selecciona tu compartimento y haz clic en Create Log Group. Se abre un panel lateral.
Introduce data_log_group para el nombre y, opcionalmente, proporciona una descripción y etiquetas (tags).
Haz clic en Create (Crear) para configurar tu nuevo grupo de logs.
En Resources (Recursos), haz clic en Logs.
Haz clic en Create custom log (Crear log personalizado) o Enable service log (Habilitar log de servicio) según lo desees.
Haz clic en Enable Log (Habilitar log), para crear tu nuevo log de OCI.

Para más información sobre logs de OCI, consulta Activación del registro para un recurso.

Función de OCI

En el portal de OCI, ve a Functions* (Funciones).
Selecciona una aplicación existente o haz clic en Create Application (Crear aplicación).
Crea una nueva función de OCI dentro de tu aplicación. Consulta Información general de funciones de Oracle para obtener más detalles.
Es recomendado para crear una función boilerplate de Python primero y reemplazar los archivos autogenerados con el código fuente de Datadog:
- Sustituye func.py por código del repositorio de Datadog OCI.
- Sustituye func.yaml por el código del repositorio de Datadog OCI. DATADOG_TOKEN y DATADOG_HOST deben sustituirse por tu clave de API de Datadog y el enlace de entrada de logs de la región.
- Sustituye requirements.txt por código del repositorio de Datadog OCI.

Hub de conectores de servicio de OCI

En el portal de OCI, navega hasta Logging -> Service Connectors (Registro > Conectores de servicio).
Haz clic en Create Service Connector (Crear conector de servicio) para ser redireccionado a la página Create Service Connector (Crear conector de servicio).
Selecciona Source (Origen) como Logging (Registro) y Target (Destino) como Functions (Funciones).
En Configure Source Connection (Configurar conexión de origen) selecciona Compartment name (Nombre de compartimento), Log Group (Grupo de logs) y Log. (El Log Group (Grupo de logs) y Log creados en el primer paso).
Si también deseas enviar Audit Logs (Logs de auditoría), haz clic en +Another Log (+ otro log) y selecciona el mismo Compartment (Compartimento) y reemplaza “_Audit” (_Auditoría) como tu Log Group (Grupo de logs).
En Configure target (Configurar destino) selecciona Compartment (Compartimento), Function application (Aplicación de función) y Function (Función). (La Function Application (Aplicación de función) y Function (Función) creadas en el paso anterior.
Si se te pide que crees una política, haz clic en Create (Crear) en la pantalla.
Haz clic en Create (Crear) en la parte inferior para terminar de crear tu conector de servicio.

Para obtener más información sobre OCI Object Storage, consulta la entrada del blog sobre el conector de servicio de Oracle.

Configura un log de OCI.
Crea un almacén de objetos de OCI y habilita el acceso de lectura/escritura para logs de OCI.
Crea una función de OCI.
Configura un evento de OCI.

Las siguientes instrucciones utilizan el portal de OCI para configurar la integración.

Registro de OCI

En el portal de OCI, ve a Solutions and Platform -> Logging -> Logs (Soluciones y plataforma -> Registro -> Logs).
Haz clic en Create Custom Log (Crear log personalizado) para pasar a la página Create Custom Log (Crear log personalizado).
Dale un nombre a tu nuevo log de OCI.
Selecciona un Compartment (Compartimento) y un Log Group (Grupo de logs). Estas selecciones se mantienen en toda la instalación.
Haz clic en Create Custom Log (Crear log personalizado) para acceder a la página Create Agent Config (Crear configuración del Agent).
Haz clic en Create new configuration (Crear nueva configuración).
Dale un nombre a tu nueva configuración. Tu compartimento está preseleccionado para ti.
Establece el tipo de grupo en Dynamic Group (Grupo dinámico) y agrupa a uno de tus grupos existentes.
Establece el tipo de entrada en Log Path (Ruta de log), introduce el nombre de entrada que prefieras y utiliza “/” para las rutas de los archivos.
Haz clic en Create Custom Log (Crear log personalizado), entonces tu log de OCI se creará y estará disponible en la página de logs.

Para más información sobre logs de OCI, consulta Activación del registro para un recurso.

OCI object storage

En el portal de OCI, ve a Core Infrastructure -> Object Storage -> Object Storage (Infraestructura central > Object Storage > Object Storage).
Haz clic en Create Bucket (Crear bucket) para acceder al formulario Create bucket (Crear bucket).
Selecciona Standard (Estándar) para tu nivel de almacenamiento y marca Emit Object Events (Emitir eventos de objeto).
Rellena el resto del formulario según tus preferencias.
Haz clic en Create Bucket (Crear bucket), tu bucket se creará y estará disponible en la lista de buckets.
Selecciona tu nuevo bucket en la lista de buckets activos y haz clic en Logs en recursos.
Activa read (leer), lo que te lleva al menú lateral Enable Log (Habilitar log).
Selecciona un Compartment (Compartimento) y un Log Group (Grupo de logs) (utiliza las mismas selecciones que en tu log de OCI).
Introduce un nombre para el Log Name (Nombre de log) y selecciona tu retención de log preferida.

Para más información sobre OCI Object Storage, consulta Poner datos en Object Storage.

Función de OCI

En el portal de OCI, ve a Solutions and Platform -> Developer Services -> Functions (Soluciones y plataforma > Servicios de desarrollador > Funciones).
Selecciona una aplicación existente o haz clic en Create Application (Crear aplicación).
Crea una nueva función de OCI dentro de tu aplicación. Para más detalles, consulta Información general de funciones de Oracle.
Es recomendado para crear una función boilerplate de Python primero y reemplazar los archivos autogenerados con el código fuente de Datadog:
- Sustituye func.py por código del repositorio de Datadog OCI.
- Sustituye func.yaml por el código del repositorio de Datadog OCI. DATADOG_TOKEN y DATADOG_HOST deben sustituirse por tu clave de API de Datadog y el enlace de entrada de logs de la región.
- Sustituye requirements.txt por código del repositorio de Datadog OCI.

Evento de OCI

En el portal de OCI, ve a Solutions and Platform -> Application Integration -> Event Service (Soluciones y plataforma > Integración de aplicaciones > Servicio de eventos).
Haz clic en Create Rule (Crear regla) para acceder a la página Create Rule (Crear regla).
Asigna un nombre y una descripción a tu regla de evento.
Establece tu condición como Event Type (Tipo de evento), el nombre de servicio como Object Storage y el tipo de evento como Object - Create (Objeto: crear).
Establece tu tipo de acción como Functions (Funciones).
Asegúrate de que tu compartimento de función sea la misma selección que hiciste para Log de OCI, Bucket de OCI y Función de OCI.
Selecciona tu aplicación de función y función (según el paso de instalación anterior).
Haz clic en Create Rule (Crear regla), tu regla se creará y estará disponible en la lista de reglas.

Para más información sobre OCI Object Storage, consulta Empezando con eventos.

Datos recopilados

Métricas

oci.autonomous_database.apply_lag (gauge)	This metric displays (in seconds) how far the standby database is behind the primary database as of the time sampled. Shown as second
oci.autonomous_database.block_changes (gauge)	The average number of blocks changed per second. Shown as update
oci.autonomous_database.cpu_time (gauge)	Average rate of accumulation of CPU time by foreground sessions in the database over the time interval. Statistic: Mean. Interval: 1 minute Shown as second
oci.autonomous_database.cpu_utilization (gauge)	The CPU usage expressed as a percentage, aggregated across all consumer groups. The utilization percentage is reported with respect to the number of CPUs the database is allowed to use. Statistic: Mean. Interval: 1 minute Shown as percent
oci.autonomous_database.current_logons (count)	The number of successful logons during the selected interval. Statistic: Count. Interval: 1 minute Shown as operation
oci.autonomous_database.dbtime (gauge)	The amount of time database user sessions spend executing database code (CPU Time + WaitTime). DB Time is used to infer database call latency, because DB Time increases in direct proportion to both database call latency (response time) and call volume. It is calculated as the average rate of accumulation of database time by foreground sessions in the database over the time interval. Shown as second
oci.autonomous_database.ecpus_allocated (gauge)	The actual number of ECPUs allocated by the service during the selected interval of time. Shown as cpu
oci.autonomous_database.execute_count (count)	The number of user and recursive calls that executed SQL statements during the selected interval. Statistic: Sum. Interval: 1 minute Shown as execution
oci.autonomous_database.iops (gauge)	The average number of I/O operations per second. Shown as operation
oci.autonomous_database.iothroughput (gauge)	The average throughput in MB per second. Shown as megabyte
oci.autonomous_database.logical_blocks_read (gauge)	The average number of logical block reads ("db block gets" plus "consistent gets") per second. Includes buffered and direct I/O. Statistic: Sum. Interval: 1 minute Shown as read
oci.autonomous_database.ocpus_allocated (gauge)	The actual number of OCPUs allocated by the service during the selected interval of time. Shown as cpu
oci.autonomous_database.parse_count (count)	The number of hard and soft parses during the selected interval. Statistic: Sum. Interval: 1 minute Shown as event
oci.autonomous_database.parses_by_type (count)	The number of hard or soft parses per second. Shown as event
oci.autonomous_database.queued_statements (count)	The number of queued SQL statements, aggregated across all consumer groups, during the selected interval. Statistic: Sum. Interval: 1 minute Shown as execution
oci.autonomous_database.redo_size (gauge)	The average amount of redo generated in MB per second. Shown as megabyte
oci.autonomous_database.running_statements (count)	The number of running SQL statements, aggregated across all consumer groups, during the selected interval. Statistic: Mean. Interval: 1 minute Shown as execution
oci.autonomous_database.sessions (count)	The number of sessions in the database. Statistic: Sum. Interval: 1 minute Shown as session
oci.autonomous_database.storage_allocated (gauge)	Maximum amount of space allocated to the database during the interval. Statistic: Max. Interval: 1 hour Shown as gigabyte
oci.autonomous_database.storage_allocated_by_tablespace (gauge)	Maximum amount of space allocated for each tablespace during the interval. Shown as gigabyte
oci.autonomous_database.storage_used (gauge)	Maximum amount of space used during the interval. Statistic: Max. Interval: 1 hour Shown as gigabyte
oci.autonomous_database.storage_used_by_tablespace (gauge)	Maximum amount of space used by each tablespace during the interval. Shown as gigabyte
oci.autonomous_database.storage_utilization (gauge)	The percentage of provisioned storage capacity currently in use. Represents the total allocated space for all tablespaces. Statistic: Mean. Interval: 1 hour Shown as percent
oci.autonomous_database.storage_utilization_by_tablespace (gauge)	The percentage of space utilized by each tablespace. Shown as percent
oci.autonomous_database.transaction_count (count)	The combined number of user commits and user rollbacks during the selected interval. Statistic: Sum. Interval: 1 minute Shown as event
oci.autonomous_database.transactions_by_status (count)	The number of committed or rolled back transactions per second. Shown as transaction
oci.autonomous_database.transport_lag (gauge)	The approximate number of seconds of redo not yet available on the standby database as of the time sampled. Shown as second
oci.autonomous_database.user_calls (count)	The combined number of logons, parses, and execute calls during the selected interval. Statistic: Sum. Interval: 1 minute Shown as event
oci.autonomous_database.wait_time (gauge)	Average rate of accumulation of non-idle wait time by foreground sessions in the database over the time interval. Statistic: Mean. Interval: 1 minute Shown as second
oci.database.block_changes (gauge)	The Average number of blocks changed per second. Shown as update
oci.database.cpu_utilization (gauge)	The CPU utilization expressed as a percentage, aggregated across all consumer groups. The utilization percentage is reported with respect to the number of CPUs the database is allowed to use, which is two times the number of OCPUs. Shown as percent
oci.database.current_logons (count)	The number of successful logons during the selected interval.
oci.database.execute_count (count)	The number of user and recursive calls that executed SQL statements during the selected interval.
oci.database.parse_count (count)	The number of hard and soft parses during the selected interval.
oci.database.storage_allocated (gauge)	Total amount of storage space allocated to the database at the collection time. Shown as gigabyte
oci.database.storage_allocated_by_tablespace (gauge)	Total amount of storage space allocated to the tablespace at the collection time. In case of container database, this metric provides root container tablespaces. Shown as gigabyte
oci.database.storage_used (gauge)	Total amount of storage space used by the database at the collection time. Shown as gigabyte
oci.database.storage_used_by_tablespace (gauge)	Total amount of storage space used by tablespace at the collection time. In case of container database, this metric provides root container tablespaces. Shown as gigabyte
oci.database.storage_utilization (gauge)	The percentage of provisioned storage capacity currently in use. Represents the total allocated space for all tablespaces. Shown as percent
oci.database.storage_utilization_by_tablespace (gauge)	This indicates the percentage of storage space utilized by the tablespace at the collection time. In case of container database, this metric provides root container tablespaces. Shown as percent
oci.database.transaction_count (count)	The combined number of user commits and user rollbacks during the selected interval. Shown as transaction
oci.database.user_calls (count)	The combined number of logons, parses, and execute calls during the selected interval.
oci.database_cluster.asmdiskgroup_utilization (gauge)	Percentage of usable space used in a Disk Group. Usable space is the space available for growth. DATA disk group stores our Oracle database files. RECO disk group contains database files for recovery such as archives and flashback logs. Shown as percent
oci.database_cluster.cpu_utilization (gauge)	Percent CPU utilization. Shown as percent
oci.database_cluster.filesystem_utilization (gauge)	Percent utilization of provisioned filesystem. Shown as percent
oci.database_cluster.load_average (gauge)	System load average over 5 minutes. Shown as process
oci.database_cluster.memory_utilization (gauge)	Percentage of memory available for starting new applications, without swapping. The available memory can be obtained via the following command: cat/proc/meminfo. Shown as percent
oci.database_cluster.node_status (gauge)	Indicates whether the host is reachable in RAC environments.
oci.database_cluster.ocpus_allocated (gauge)	The number of OCPUs allocated. Shown as cpu
oci.database_cluster.swap_utilization (gauge)	Percent utilization of total swap space. Shown as percent
oci.blockstore.volume_guaranteed_iops (gauge)	Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. Shown as operation
oci.blockstore.volume_guaranteed_throughput (gauge)	Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. Shown as megabyte
oci.blockstore.volume_guaranteed_vpus_per_gb (gauge)	Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. Shown as operation
oci.blockstore.volume_read_ops (count)	Activity level from I/O reads. Expressed as reads per interval. Shown as operation
oci.blockstore.volume_read_throughput (gauge)	Read throughput. Expressed as bytes read per interval. Shown as byte
oci.blockstore.volume_replication_seconds_since_last_sync (gauge)	Time elapsed since the last synced cross region replica. Expressed in seconds. Shown as second
oci.blockstore.volume_replication_seconds_since_last_upload (gauge)	Time elapsed since the last cross region replica was uploaded. Expressed in seconds. Shown as second
oci.blockstore.volume_throttled_ios (count)	Total sum of all the I/O operations that were throttled during a given time interval. Shown as operation
oci.blockstore.volume_write_ops (count)	Activity level from I/O writes. Expressed as writes per interval. Shown as operation
oci.blockstore.volume_write_throughput (gauge)	Write throughput. Expressed as bytes written per interval. Shown as byte
oci.gpu_infrastructure_health.gpu_ecc_double_bit_errors (count)	The number of GPU double bit ECC errors reported. Shown as error
oci.gpu_infrastructure_health.gpu_ecc_single_bit_errors (count)	The number of GPU single bit ECC errors reported. Shown as error
oci.gpu_infrastructure_health.gpu_memory_utilization (gauge)	The percentage of the GPU memory resource in use. Shown as percent
oci.gpu_infrastructure_health.gpu_power_draw (gauge)	The amount of GPU power used.
oci.gpu_infrastructure_health.gpu_temperature (gauge)	The GPU temperature reported.
oci.gpu_infrastructure_health.gpu_utilization (gauge)	Activity level from GPU. Expressed as a percentage of total time. For instance pools, the value is averaged across all instances in the pool. Shown as percent
oci.computeagent.cpu_utilization (gauge)	Activity level from CPU. Expressed as a percentage of total time. For instance pools, the value is averaged across all instances in the pool. Shown as percent
oci.computeagent.disk_bytes_read (count)	Read throughput. Expressed as bytes read per interval. Shown as byte
oci.computeagent.disk_bytes_written (count)	Write throughput. Expressed as bytes written per interval. Shown as byte
oci.computeagent.disk_iops_read (count)	Activity level from I/O reads. Expressed as reads per interval. Shown as operation
oci.computeagent.disk_iops_written (count)	Activity level from I/O writes. Expressed as writes per interval. Shown as operation
oci.computeagent.load_average (gauge)	Average system load calculated over a 1-minute period. Shown as process
oci.computeagent.memory_allocation_stalls (count)	Number of times page reclaim was called directly.
oci.computeagent.memory_utilization (gauge)	Space currently in use. Measured by pages. Expressed as a percentage of used pages. For instance pools, the value is averaged across all instances in the pool. Shown as percent
oci.computeagent.networks_bytes_in (count)	Network receipt throughput. Expressed as bytes received. Shown as byte
oci.computeagent.networks_bytes_out (count)	Network transmission throughput. Expressed as bytes transmitted. Shown as byte
oci.rdma_infrastructure_health.rdma_rx_bytes (count)	The bytes received on the RDMA interface. Shown as byte
oci.rdma_infrastructure_health.rdma_rx_packets (count)	The number of RDMA interface packets received. Shown as packet
oci.rdma_infrastructure_health.rdma_tx_bytes (count)	The bytes transmitted on the RDMA interface. Shown as byte
oci.rdma_infrastructure_health.rdma_tx_packets (count)	The number of RDMA interface packets transmitted. Shown as packet
oci.compute_infrastructure_health.health_status (count)	The number of health issues for an instance. Any non-zero value indicates a health defect. This metric is available only for bare metal instances. Shown as error
oci.compute_infrastructure_health.instance_status (gauge)	The status of a running instance. A value of 0 indicates that the instance is available (up). A value of 1 indicates that the instance is not available (down) due to an infrastructure issue. If the instance is stopped, then the metric does not have a value. This metric is available only for VM instances. Shown as instance
oci.compute_infrastructure_health.maintenance_status (gauge)	The maintenance status of an instance. A value of 0 indicates that the instance is not scheduled for an infrastructure maintenance event. A value of 1 indicates that the instance is scheduled for an infrastructure maintenance event. This metric is available for both VM and bare metal instances. Shown as instance
oci.oracle_oci_database.allocated_storage_utilization_by_tablespace (gauge)	The percentage of space used by a tablespace, out of allocated space. Shown as percent
oci.oracle_oci_database.apply_lag (gauge)	The number of seconds the standby database is behind the primary database. Statistic: Mean Interval: 5 minutes Resource group: oracle_dataguard Not applicable for PDBs. Shown as second
oci.oracle_oci_database.apply_lag_data_refresh_elapsed_time (gauge)	The elapsed time since the ApplyLag metric sample was last collected. Statistic: Mean Interval: 5 minutes Resource group: oracle_dataguard Not applicable for PDBs. Shown as second
oci.oracle_oci_database.avg_gc_cr_block_receive_time (gauge)	The average global cache consistent-read (CR) block receive time. Shown as millisecond
oci.oracle_oci_database.backup_duration (gauge)	The duration of the last database backup. Statistic: Mean Interval: 30 minutes Only applicable for SI and RAC CDBs. Shown as second
oci.oracle_oci_database.backup_size (gauge)	The size of the last database backup. Statistic: Mean Interval: 30 minutes Only applicable for SI and RAC CDBs. Shown as gigabyte
oci.oracle_oci_database.block_changes (gauge)	The average number of blocks changed per second. Shown as update
oci.oracle_oci_database.blocking_sessions (gauge)	The current blocking sessions.
oci.oracle_oci_database.cputime (gauge)	The average rate of accumulation of CPU time by foreground sessions in the database instance over the time interval. The CPU time component of Average Active Sessions. Shown as fraction
oci.oracle_oci_database.cpu_utilization (gauge)	The CPU utilization expressed as a percentage, aggregated across all consumer groups. The utilization percentage is reported with respect to the number of CPUs the database is allowed to use, which is two times the number of OCPUs. Shown as percent
oci.oracle_oci_database.current_logons (count)	The number of successful logons during the selected interval.
oci.oracle_oci_database.dbtime (gauge)	The average rate of accumulation of database time (CPU + Wait) by foreground sessions in the database instance over the time interval. Also known as Average Active Sessions. Shown as fraction
oci.oracle_oci_database.estimated_failover_time (gauge)	The number of seconds required to fail over to the standby database. Statistic: Mean. Interval: 5 minutes. Resource group: oracle_dataguard. Not applicable for PDBs. Shown as second
oci.oracle_oci_database.execute_count (count)	The number of user and recursive calls that executed SQL statements during the selected interval. Shown as execution
oci.oracle_oci_database.fraspace_limit (gauge)	The flash recovery area space limit. Shown as gigabyte
oci.oracle_oci_database.frautilization (gauge)	The flash recovery area utilization. Shown as percent
oci.oracle_oci_database.gc_cr_blocks_received (gauge)	The global cache CR blocks received per second. Shown as block
oci.oracle_oci_database.gc_current_blocks_received (gauge)	The global cache current blocks received per second. Shown as block
oci.oracle_oci_database.iops (gauge)	The average number of IO operations per second. Shown as operation
oci.oracle_oci_database.io_throughput (gauge)	The average throughput in MB per second. Shown as megabyte
oci.oracle_oci_database.interconnect_traffic (gauge)	The average internode data transfer rate. Shown as megabyte
oci.oracle_oci_database.invalid_objects (gauge)	The number of invalid database objects.
oci.oracle_oci_database.logical_blocks_read (gauge)	The average number of blocks read from SGA/Memory (buffer cache) per second. Shown as read
oci.oracle_oci_database.max_tablespace_size (gauge)	The maximum possible tablespace size. For CDBs, this metric provides data for root container tablespaces. Shown as gigabyte
oci.oracle_oci_database.memory_usage (gauge)	The total size of the memory pool. Shown as megabyte
oci.oracle_oci_database.monitoring_status (gauge)	The monitoring status of the resource. If a metric collection fails, error information is captured in this metric.
oci.oracle_oci_database.non_reclaimable_fra (gauge)	The non-reclaimable fast recovery area. Shown as percent
oci.oracle_oci_database.ocpus_allocated (count)	The actual number of OCPUs allocated by the service during the selected interval of time.
oci.oracle_oci_database.parse_count (count)	The number of hard and soft parses during the selected interval.
oci.oracle_oci_database.parses_by_type (gauge)	The number of hard or soft parses per second. Shown as event
oci.oracle_oci_database.problematic_scheduled_dbmsjobs (gauge)	The number of problematic scheduled database jobs. Shown as job
oci.oracle_oci_database.process_limit_utilization (gauge)	The process limit utilization. Shown as percent
oci.oracle_oci_database.processes (gauge)	The number of database processes. Shown as process
oci.oracle_oci_database.reclaimable_fra (gauge)	The reclaimable fast recovery area. Shown as percent
oci.oracle_oci_database.reclaimable_fraspace (gauge)	The flash recovery area reclaimable space. Shown as gigabyte
oci.oracle_oci_database.recovery_window (gauge)	The current recovery window of a database. Statistic: Mean. Interval: 15 minutes. Only applicable for SI and RAC CDBs version 19c and later. Shown as second
oci.oracle_oci_database.redo_apply_rate (gauge)	The redo apply rate on the standby database. Statistic: Mean. Interval: 5 minutes. Resource group: oracle_dataguard. Not applicable for PDBs. Shown as megabyte
oci.oracle_oci_database.redo_generation_rate (gauge)	The redo generation rate on the primary database. Statistic: Mean. Interval: 5 minutes. Resource group: oracle_dataguard. Not applicable for PDBs. Shown as megabyte
oci.oracle_oci_database.redo_size (gauge)	The average amount of redo generated. Shown as megabyte
oci.oracle_oci_database.session_limit_utilization (gauge)	The session limit utilization. Shown as percent
oci.oracle_oci_database.sessions (gauge)	The number of sessions in the database. Shown as session
oci.oracle_oci_database.storage_allocated (gauge)	The total amount of storage space allocated to the database at collection time. Shown as gigabyte
oci.oracle_oci_database.storage_allocated_by_tablespace (gauge)	The total amount of storage space allocated to the tablespace at collection time. In the case of CDBs, this metric provides root container tablespaces. Shown as gigabyte
oci.oracle_oci_database.storage_used (gauge)	The total storage used by the database at collection time, including the space used by tablespaces, flash recovery area, control files, and log files. Shown as gigabyte
oci.oracle_oci_database.storage_used_by_tablespace (gauge)	The total amount of storage space used by tablespace at collection time. In the case of CDBs, this metric provides root container tablespace. Shown as gigabyte
oci.oracle_oci_database.storage_utilization (gauge)	The percentage of provisioned storage capacity currently in use. Represents the total allocated space for all tablespaces. Shown as percent
oci.oracle_oci_database.storage_utilization_by_tablespace (gauge)	The percentage of storage space utilized by the tablespace at the collection time. In the case of CDBs, this metric provides root container tablespaces. Shown as percent
oci.oracle_oci_database.transaction_count (count)	The combined number of user commits and user rollbacks during the selected interval. Shown as transaction
oci.oracle_oci_database.transactions_by_status (gauge)	The number of committed or rolled back transactions per second. Shown as transaction
oci.oracle_oci_database.transport_lag (gauge)	The number of seconds of redo not yet available on the standby database. Statistic: Mean. Interval: 5 minutes. Resource group: oracle_dataguard. Not applicable for PDBs. Shown as second
oci.oracle_oci_database.transport_lag_data_refresh_elapsed_time (gauge)	The elapsed time since the TransportLagDataRefreshElapsedTime metric sample was last collected. Statistic: Mean. Interval: 5 minutes. Resource group: oracle_dataguard. Not applicable for PDBs. Shown as second
oci.oracle_oci_database.unprotected_data_window (gauge)	The current unprotected data window of a database. Statistic: Mean. Interval: 15 minutes. Only applicable for SI and RAC CDBs version 19c and later. Shown as second
oci.oracle_oci_database.unusable_indexes (gauge)	The number of unusable indexes in the database schema. Shown as index
oci.oracle_oci_database.usable_fra (gauge)	The usable fast recovery area. Shown as percent
oci.oracle_oci_database.used_fraspace (gauge)	The flash recovery area space usage. Shown as gigabyte
oci.oracle_oci_database.user_calls (count)	The combined number of logons, parses, and execute calls during the selected interval.
oci.oracle_oci_database.wait_time (gauge)	The average rate of accumulation of non-idle wait time by foreground sessions in the database instance over the time interval. The wait time component of Average Active Sessions. Shown as fraction
oci.oracle_oci_database.dbmgmt_job_executions_count (count)	The number of SQL job executions on a single Managed Database or a Database Group, and their status. Shown as execution
oci.fastconnect.bits_received (count)	Number of bits received on the FastConnect interface at the Oracle end of the connection. For a cross-connect group (LAG), the value is the sum across all cross-connects in the group. Shown as bit
oci.fastconnect.bits_sent (count)	Number of bits sent from the FastConnect interface at the Oracle end of the connection. For a cross-connect group (LAG), the value is the sum across all cross-connects in the group. Shown as bit
oci.fastconnect.bytes_received (count)	Number of bytes received on the FastConnect interface at the Oracle end of the connection. For a cross-connect group (LAG), the value is the sum across all cross-connects in the group. Shown as byte
oci.fastconnect.bytes_sent (count)	Number of bytes sent from the FastConnect interface at the Oracle end of the connection. For a cross-connect group (LAG), the value is the sum across all cross-connects in the group. Shown as byte
oci.fastconnect.connection_state (gauge)	The values are up (1) or down (0). For a virtual circuit, the operational state of the virtual circuit's interface. For a cross-connect group, this reflects the overall operational state of the cross-connects that make up the cross-connect group (LAG). If at least one of the cross-connects is up, this value is up (1). If all the cross-connects in the group are down, this value is down (0).
oci.fastconnect.ipv_4bgp_session_state (gauge)	The values are up (1) or down (0). The status of the IPv4 BGP session for a virtual circuit.
oci.fastconnect.ipv_6bgp_session_state (gauge)	The values are up (1) or down (0). The status of the IPv6 BGP session for a virtual circuit.
oci.fastconnect.packets_discarded (count)	Number of packets discarded at the Oracle end of the connection. Shown as packet
oci.fastconnect.packets_error (count)	Number of packets dropped at the Oracle end of the connection. Dropped packets indicate a misconfiguration in some part of the overall system. Check if there's been a change to the configuration of your VCN, the virtual circuit, or your CPE. For a cross-connect group (LAG), the value is the sum across all cross-connects in the group. Shown as packet
oci.fastconnect.packets_received (count)	Number of packets received on the FastConnect interface at the Oracle end of the connection. For a cross-connect group (LAG), the value is the sum across all cross-connects in the group. Shown as packet
oci.fastconnect.packets_sent (count)	Number of packets sent from the FastConnect interface at the Oracle end of the connection. For a cross-connect group (LAG), the value is the sum across all cross-connects in the group. Shown as packet
oci.filestorage.file_system_read_average_latency_by_size (gauge)	Read latency by size. Expressed as average read latency per second, grouped by size. Shown as second
oci.filestorage.file_system_read_requests_by_size (gauge)	Read requests by size. Expressed as operation per second, grouped by size. Shown as operation
oci.filestorage.file_system_read_throughput (count)	Read throughput for the file system. If the file system is exported through multiple mount targets, total throughput for all mount targets is displayed. Expressed as bytes read per second. Shown as byte
oci.filestorage.file_system_usage (gauge)	Total space utilization for a file system. Expressed as GiB consumed per second. Shown as byte
oci.filestorage.file_system_write_average_latency_by_size (gauge)	Write latency by size. Expressed as average write latency per second, grouped by size. Shown as second
oci.filestorage.file_system_write_requests_by_size (count)	Write requests by size. Expressed as operation per second, grouped by size. Shown as operation
oci.filestorage.file_system_write_throughput (count)	Write throughput for the file system. If the file system is exported through multiple mount targets, total throughput for all mount targets is displayed. Expressed as bytes written per second. Shown as byte
oci.filestorage.kerberos_errors (count)	Kerberos errors seen by the mount target while receiving IO from an NFS client. Expressed as a sum of errors per interval. Shown as error
oci.filestorage.ldap_connection_errors (count)	Connection failures between mount targets and the LDAP server for this outbound connector. Expressed as error count by error type per interval. Shown as error
oci.filestorage.ldap_request_average_latency (gauge)	Mount target to LDAP server request latency for this outbound connector. Expressed as mean latency, in seconds, by request type. Shown as second
oci.filestorage.ldap_request_errors (count)	LDAP query failures over an established connection between mount targets and the LDAP server for this outbound connector. Expressed as error count by error type per interval. Shown as error
oci.filestorage.ldap_request_throughput (count)	Requests from the mount target to the LDAP server through its outbound connector. Expressed as request type and outbound connector per interval. Shown as request
oci.filestorage.metadata_iops (gauge)	IOPs (Input/Output Operations Per Second) for the following NFS operations: CREATE, GETATTR, SETATTR, and REMOVE. Expressed as operations per second. Shown as operation
oci.filestorage.metadata_request_average_latency (gauge)	Average metadata request latency for the following NFS operations: CREATE, GETATTR, SETATTR, and REMOVE. Expressed as average latency per second, grouped by operation. Shown as second
oci.filestorage.mount_target_connections (count)	Number of client connections for the mount target. Expressed as total connection count at the interval. Shown as connection
oci.filestorage.mount_target_health (gauge)	Number of successfully executed NFS API requests. Expressed as a percentage of total requests per interval. Shown as percent
oci.filestorage.mount_target_read_throughput (count)	Read throughput for the mount target. If the mount target exports multiple file systems, total throughput for all file systems is displayed. Expressed as bytes read per interval. Shown as byte
oci.filestorage.mount_target_write_throughput (count)	Write throughput for the mount target. If the mount target exports multiple file systems, total throughput for all file systems is displayed. Expressed as bytes written per interval. Shown as byte
oci.filestorage.replication_egress_throughput (count)	Data that has been copied out of the source region. Only applicable for cross-region replication. Expressed as a sum of bytes written per interval. Shown as byte
oci.filestorage.replication_recovery_point_age (gauge)	Age of the last fully copied snapshot that was applied to the target file system. Or, how much older the data on the target file system is than the source file system. Expressed as time since the source snapshot was taken. Monitor this metric to ensure that the data on the target file system isn't older than your requirements allow (RPO). Shown as time
oci.filestorage.replication_throughput (count)	Throughput of the data transferred out of the source file system. Expressed as bytes read per interval. Shown as byte
oci.faas.allocated_provisioned_concurrency (gauge)	Memory consumed by provisioned concurrency slots. Shown as megabyte
oci.faas.allocated_total_concurrency (gauge)	Total concurrent memory allocated. Shown as megabyte
oci.faas.function_execution_duration (count)	Total function execution duration. Expressed in milliseconds. Shown as millisecond
oci.faas.function_invocation_count (count)	Total number of function invocations.
oci.faas.function_response_count (count)	Total number of function responses. Shown as invocation
oci.lbaas.accepted_connections (count)	The number of connections accepted by the load balancer. Shown as connection
oci.lbaas.accepted_sslhandshake (count)	The number of accepted SSL handshakes. Shown as operation
oci.lbaas.active_connections (count)	The number of active connections from clients to the load balancer. Shown as connection
oci.lbaas.active_sslconnections (count)	The number of active SSL connections. Shown as connection
oci.lbaas.backend_servers (gauge)	The number of backend servers in the backend set. Shown as instance
oci.lbaas.backend_timeouts (count)	The number of timeouts across all backend servers. Shown as timeout
oci.lbaas.bytes_received (count)	The number of bytes received by the load balancer. Shown as byte
oci.lbaas.bytes_sent (count)	The number of bytes sent across all backend servers. Shown as byte
oci.lbaas.closed_connections (count)	The number of connections closed between the load balancer and backend servers. Shown as connection
oci.lbaas.failed_sslclient_cert_verify (count)	The number of failed client SSL certificate verifications. Shown as error
oci.lbaas.failed_sslhandshake (count)	The number of failed SSL handshakes. Shown as error
oci.lbaas.handled_connections (count)	The number of connections handled by the load balancer. Shown as connection
oci.lbaas.http_requests (count)	The number of incoming client requests to the backend set. Shown as request
oci.lbaas.http_responses (count)	The number of HTTP responses across all backend servers. Shown as response
oci.lbaas.http_responses_200 (count)	The number of HTTP 200 responses received from backend sets. Shown as response
oci.lbaas.http_responses_2xx (count)	The number of HTTP 2xx responses received from backend sets. Shown as response
oci.lbaas.http_responses_3xx (count)	The number of HTTP 3xx responses received from backend sets. Shown as response
oci.lbaas.http_responses_4xx (count)	The number of HTTP 4xx responses received from backend sets. Shown as response
oci.lbaas.http_responses_502 (count)	The number of HTTP 502 responses received from backend sets. Shown as response
oci.lbaas.http_responses_504 (count)	The number of HTTP 504 responses received from backend sets. Shown as response
oci.lbaas.http_responses_5xx (count)	The number of HTTP 5xx responses received from backend sets. Shown as response
oci.lbaas.http_responses_200 (count)	The number of HTTP 200 responses received from backend servers. Shown as response
oci.lbaas.http_responses_2xx (count)	The number of HTTP 2xx responses received from backend servers. Shown as response
oci.lbaas.http_responses_3xx (count)	The number of HTTP 3xx responses received from backend servers. Shown as response
oci.lbaas.http_responses_4xx (count)	The number of HTTP 4xx responses received from backend servers. Shown as response
oci.lbaas.http_responses_502 (count)	The number of HTTP 502 responses received from backend servers. Shown as response
oci.lbaas.http_responses_504 (count)	The number of HTTP 504 responses received from backend servers. Shown as response
oci.lbaas.http_responses_5xx (count)	The number of HTTP 5xx responses received from backend servers. Shown as response
oci.lbaas.invalid_header_responses (count)	The number of invalid header responses across all backend servers. Shown as response
oci.lbaas.keep_alive_connections (count)	The number of keep-alive connections. Shown as connection
oci.lbaas.peak_bandwidth (gauge)	Maximum bits per second bandwidth used during the specified interval. Shown as bit
oci.lbaas.response_time_first_byte (gauge)	Average time to the first byte of response from backend servers. TCP only. Shown as millisecond
oci.lbaas.response_time_http_header (gauge)	Average response time of backend servers. HTTP only. Shown as millisecond
oci.lbaas.unhealthy_backend_servers (gauge)	The number of unhealthy backend servers in the backend set. Shown as instance
oci.mediastreams.egress_bytes (count)	Total egress of data streamed through the Distribution Channel (in GB). Shown as byte
oci.mediastreams.request_count (count)	Total number of requests made to the Distribution Channel. Shown as request
oci.mysql_database.active_connections (gauge)	The number of connections actively executing statements against the MySQL DB system. Shown as connection
oci.mysql_database.backup_failure (gauge)	Backup failure events observed over the last interval. 0 - OK 1 - FAILED
oci.mysql_database.backup_size (gauge)	The aggregate size of all backups per DB system. Shown as byte
oci.mysql_database.backup_time (gauge)	The time taken to create a backup. Shown as millisecond
oci.mysql_database.cpuutilization (gauge)	CPU utilization for the MySQL DB system host or HeatWave nodes. Shown as percent
oci.mysql_database.channel_failure (gauge)	The channel health status observed over the last interval. One of the following values: 0 - HEALTHY 1 - FAILED To troubleshoot inbound replication failure, see Troubleshooting Inbound Replication.
oci.mysql_database.channel_lag (gauge)	The channel lag, with respect to the immediate source of the channel, observed over the last interval. If the channel is configured with replication delay, the channel lag includes the replication delay. See Creating a Replication Channel. Shown as millisecond
oci.mysql_database.current_connections (gauge)	The number of current connections to the MySQL DB system. Shown as connection
oci.mysql_database.db_volume_read_bytes (count)	The total bytes read from the MySQL DB system volume(s). Shown as byte
oci.mysql_database.db_volume_read_operations (count)	The total number of read operations for the DB volume(s). Shown as operation
oci.mysql_database.db_volume_utilization (gauge)	The total space utilization of the MySQL DB system volume(s). Shown as percent
oci.mysql_database.db_volume_write_bytes (count)	The total bytes written to the MySQL DB system volume(s). Shown as byte
oci.mysql_database.db_volume_write_operations (count)	The total number of write operations for the MySQL DB volume(s). Shown as operation
oci.mysql_database.heat_wave_data_load_progress (gauge)	Progress of data load into HeatWave cluster memory. Shown as percent
oci.mysql_database.heat_wave_health (gauge)	HeatWave cluster health status. One of the following values: 0 - HEALTHY 0.5: RELOADING DATA 1 - RECOVERING 2 - FAILED See HeatWave Cluster Failure and Recovery.
oci.mysql_database.heat_wave_statements (count)	The number of statements executed against the MySQL DB System and were executed on HeatWave cluster.
oci.mysql_database.memory_allocated (gauge)	The total amount of memory allocated during the selected interval. Shown as gigabyte
oci.mysql_database.memory_used (gauge)	The maximum amount of memory used during the selected interval. Shown as gigabyte
oci.mysql_database.memory_utilization (gauge)	Memory utilization for the MySQL DB system host or HeatWave nodes. Shown as percent
oci.mysql_database.network_receive_bytes (count)	Network receive bytes for the MySQL DB system. Shown as byte
oci.mysql_database.network_transmit_bytes (count)	Network transmit bytes for the MySQL DB system. Shown as byte
oci.mysql_database.ocpus_allocated (gauge)	The actual number of OCPUs allocated during the selected interval.
oci.mysql_database.ocpus_used (gauge)	The actual number of OCPUs used during the selected interval.
oci.mysql_database.statement_latency (gauge)	Statement latency for all executed statements. Shown as millisecond
oci.mysql_database.statements (count)	The number of statements executed against the MySQL DB system.
oci.mysql_database.storage_allocated (gauge)	The maximum amount of space allocated to the DB system during the interval. Shown as gigabyte
oci.mysql_database.storage_used (gauge)	The maximum amount of space used during the interval. Shown as gigabyte
oci.nat_gateway.bytes_from_natgw (count)	Number of bytes sent from NAT gateway to OCI resources. Shown as byte
oci.nat_gateway.bytes_to_natgw (count)	Number of bytes sent from Oracle Cloud Infrastructure (OCI) resources to NAT gateway. Shown as byte
oci.nat_gateway.connections_closed (count)	Number of connections via NAT gateway that were closed by the internet host
oci.nat_gateway.connections_established (count)	Number of connections established via NAT gateway
oci.nat_gateway.connections_timed_out (count)	Number of connections closed by NAT gateway due to idle time out
oci.nat_gateway.drops_to_natgw (count)	Number of packets from OCI resources to NAT Gateway that were dropped by NAT Gateway. Shown as packet
oci.nat_gateway.packets_from_natgw (count)	Number of packets sent from NAT gateway to OCI resources. Shown as packet
oci.nat_gateway.packets_to_natgw (count)	Number of packets sent from OCI resources to NAT gateway. Shown as packet
oci.network_firewall.byte_received_count (count)	The number of bytes received through the firewall. Shown as byte
oci.network_firewall.byte_sent_count (count)	The number of bytes sent through the firewall. Shown as byte
oci.network_firewall.decryption_rule_hit_count (count)	The number of times a connection matches a decryption rule.
oci.network_firewall.icmp_fragment_attacks_count (count)	The number of ICMP fragment attacks detected.
oci.network_firewall.ip_spoof_count (count)	Number of IP spoof attacks detected.
oci.network_firewall.land_attacks_count (count)	The number of land attacks detected.
oci.network_firewall.mac_spoof_count (count)	The number of MAC spoof attacks detected.
oci.network_firewall.packet_drop_count (count)	The number of packets dropped through the firewall. Shown as packet
oci.network_firewall.packet_received_count (count)	The number of packets received at the firewall from the network, after drops. Shown as packet
oci.network_firewall.packet_received_in_error_count (count)	Number of packets received through the firewall that have errors. Shown as packet
oci.network_firewall.packet_sent_count (count)	The number of packets sent from the firewall to the network, after drops. Shown as packet
oci.network_firewall.ping_of_death_attacks_count (count)	The number of ping of death attacks detected.
oci.network_firewall.security_rule_hit_count (count)	The number of times a connection matches a security rule.
oci.network_firewall.teardrop_attacks_count (count)	The number of teardrop attacks detected.
oci.objectstorage.all_requests (count)	The total number of all HTTP requests made in a bucket. Emit frequency: every 100 ms Shown as request
oci.objectstorage.client_errors (count)	The total number of 4xx errors for requests made in a bucket. Emit frequency: every 100 ms Shown as error
oci.objectstorage.enabled_olm (gauge)	Indicates whether a bucket has any executable Object Lifecycle Management policies configured. EnabledOLM emits: 1 if policies are configured 0 if no policies are configured Emit frequency: every 3 hours
oci.objectstorage.first_byte_latency (gauge)	The per-request time measured from the time Object Storage receives the complete request to when Object Storage returns the first byte of the response. Emit frequency: every 100 ms Shown as millisecond
oci.objectstorage.object_count (count)	The count of objects in the bucket, excluding any multipart upload parts that have not been discarded (aborted) or committed. Emit frequency: every hour
oci.objectstorage.post_requests (count)	The total number of HTTP Post requests made in a bucket. Emit frequency: every 100 ms Shown as request
oci.objectstorage.put_requests (count)	The total number of PutObject requests made in a bucket. Emit frequency: every 100 ms Shown as request
oci.objectstorage.stored_bytes (gauge)	The size of the bucket, excluding any multipart upload parts that have not been discarded (aborted) or committed. Emit frequency: every hour Shown as byte
oci.objectstorage.total_request_latency (gauge)	The per-request time from the first byte received by Object Storage to the last byte sent from Object Storage. Emit frequency: every 100 ms Shown as millisecond
oci.objectstorage.uncommitted_parts (gauge)	The size of any multipart upload parts that have not been discarded (aborted) or committed. Emit frequency: every hour Shown as byte
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.
oci.postgresql.buffer_cache_hit_ratio (gauge)	The percentage of pages found in the buffer cache without reading from disk. Shown as percent
oci.postgresql.connections (count)	The number of database connections. Shown as connection
oci.postgresql.cpu_utilization (gauge)	The CPU utilization expressed as a percentage. The utilization percentage is reported with respect to the number of CPUs the database is allowed to use, which is two times the number of OCPUs. Shown as percent
oci.postgresql.deadlocks (count)	The number of locks on a database row where two or more transactions are waiting for another transaction to give up a locked row. Shown as lock
oci.postgresql.memory_utilization (gauge)	The percentage of total RAM that's in use. Shown as percent
oci.postgresql.read_iops (gauge)	The number of reads per second. Shown as read
oci.postgresql.read_latency (gauge)	Read latency in milliseconds. Shown as millisecond
oci.postgresql.read_throughput (gauge)	Reads in kilobytes per second. Shown as kilobyte
oci.postgresql.used_storage (gauge)	The amount of storage used, expressed in GB. Shown as gigabyte
oci.postgresql.write_iops (gauge)	The number of writes per second. Shown as write
oci.postgresql.write_latency (gauge)	Write latency in milliseconds. Shown as millisecond
oci.postgresql.write_throughput (gauge)	Writes in kilobytes per second. Shown as kilobyte
oci.queue.consumer_lag (gauge)	Difference in time between the oldest message in the queue and the current time Shown as minute
oci.queue.messages_count (count)	Count of messages sent and received per queue Shown as message
oci.queue.messages_in_queue_count (gauge)	Count of messages in the queue
oci.queue.queue_size (gauge)	Bytes in the queue Shown as byte
oci.queue.request_success (count)	Indicates the success of the requests sent and received per queue
oci.queue.requests_latency (gauge)	Latency of the requests to the queue Shown as millisecond
oci.queue.requests_throughput (gauge)	Bytes sent and received per queue Shown as byte
oci.service_connector_hub.bytes_read_from_source (count)	Number of bytes read from the source. Note: This value is emitted each time Connector Hub reads data from the source. If failures occur at the task or destination and Connector Hub needs to reread data from the source, the value is emitted again. Shown as byte
oci.service_connector_hub.bytes_read_from_task (count)	Number of bytes moved from the task to Connector Hub. Shown as byte
oci.service_connector_hub.bytes_written_to_target (count)	Number of bytes written to the target. Note: Use this metric as a general indicator of success. BytesWrittenToTarget might not match BytesReadFromSource or BytesReadFromTask. For example, consider a 10MB read intended for an Object Storage target. Connector Hub might compress the data, converting 10MB read into 1MB written. Shown as byte
oci.service_connector_hub.bytes_written_to_task (count)	Number of bytes moved by Connector Hub to the task. Shown as byte
oci.service_connector_hub.data_freshness (gauge)	Indicates age of the oldest processed record of the most recent set. Shown as millisecond
oci.service_connector_hub.errors_at_source (count)	Number of errors that affect retrieving data from source. Tip: To troubleshoot errors, view the errorCode and errorType dimension values. For example, an errorCode value that starts with 5, such as 500, implies a partner service outage, while the errorCode value –1 implies a network outage or timeout. Shown as error
oci.service_connector_hub.errors_at_target (count)	Number of errors that affect writing data to target. Tip: To troubleshoot errors, view the errorCode and errorType dimension values. For example, an errorCode value that starts with 5, such as 500, implies a partner service outage, while the errorCode value –1 implies a network outage or timeout. Shown as error
oci.service_connector_hub.errors_at_task (count)	Number of errors while writing to the task. Tip: To troubleshoot errors, view the errorCode and errorType dimension values. For example, an errorCode value that starts with 5, such as 500, implies a partner service outage, while the errorCode value –1 implies a network outage or timeout. Shown as error
oci.service_connector_hub.latency_at_source (gauge)	Time-to-first-byte when retrieving data from source. Useful for customers to troubleshoot with complex tasks (log rules). Shown as millisecond
oci.service_connector_hub.latency_at_target (gauge)	Time-to-first-byte when writing data to target. Shown as millisecond
oci.service_connector_hub.latency_at_task (gauge)	Time-to-first-byte for task; includes latency reading from the source, errors at the task, and errors writing to the target. Shown as millisecond
oci.service_connector_hub.messages_read_from_source (count)	Number of records read from the source. Note: The value for this metric is cumulative. Shown as message
oci.service_connector_hub.messages_read_from_task (count)	Number of messages moved from the task to Connector Hub. Shown as message
oci.service_connector_hub.messages_written_to_target (count)	Number of records written to the target. Shown as message
oci.service_connector_hub.messages_written_to_task (count)	Number of messages moved by Connector Hub to the task. Shown as message
oci.service_connector_hub.service_connector_hub_errors (count)	Number of errors in Connector Hub that affect moving data from source to target. Shown as error
oci.service_gateway.bytes_from_service (count)	The number of bytes successfully sent from the service gateway toward customer instances. Shown as byte
oci.service_gateway.bytes_to_service (count)	The number of bytes successfully sent from the service gateway toward Oracle services. Shown as byte
oci.service_gateway.packets_from_service (count)	The number of packets successfully sent from the service gateway toward customer instances. Shown as packet
oci.service_gateway.packets_to_service (count)	The number of packets successfully sent from the service gateway toward Oracle services. Shown as packet
oci.service_gateway.sgw_drops_from_service (count)	The number of packets dropped while sending packets from the service gateway toward customer instances. Shown as packet
oci.service_gateway.sgw_drops_to_service (count)	The number of packets dropped while sending packets from the service gateway toward Oracle services. Shown as packet
oci.vcn.smartnic_buffer_drops_from_host (count)	Number of packets dropped in SmartNIC from host due to buffer exhaustion. Shown as packet
oci.vcn.smartnic_buffer_drops_from_network (count)	Number of packets dropped in SmartNIC from network due to buffer exhaustion. Shown as packet
oci.vcn.vnic_conntrack_is_full (gauge)	Boolean (0/false, 1/true) that indicates the connection tracking table is full.
oci.vcn.vnic_conntrack_util_percent (gauge)	Total utilization percentage (0-100%) of the connection tracking table. Shown as percent
oci.vcn.vnic_egress_drops_conntrack_full (count)	Packets sent from the VNIC, destined for the network, dropped due to full connection tracking table. Shown as packet
oci.vcn.vnic_egress_drops_security_list (count)	Packets sent by the VNIC, destined for the network, dropped due to security rule violations. Shown as packet
oci.vcn.vnic_egress_drops_throttle (count)	Packets sent from the VNIC, destined for the network, dropped due to throttling. Shown as packet
oci.vcn.vnic_from_network_bytes (count)	Bytes received at the VNIC from the network, after drops. Shown as byte
oci.vcn.vnic_from_network_packets (count)	Packets received at the VNIC from the network, after drops. Shown as packet
oci.vcn.vnic_ingress_drops_conntrack_full (count)	Packets received from the network, destined for the VNIC, dropped due to full connection tracking table. Shown as packet
oci.vcn.vnic_ingress_drops_security_list (count)	Packets received from the network, destined for the VNIC, dropped due to security rule violations. Shown as packet
oci.vcn.vnic_ingress_drops_throttle (count)	Packets received from the network, destined for the VNIC, dropped due to throttling. Shown as packet
oci.vcn.vnic_to_network_bytes (count)	Bytes sent from the VNIC to the network, before drops. Shown as byte
oci.vcn.vnic_to_network_packets (count)	Packets sent from the VNIC to the network, before drops. Shown as packet
oci.vpn.bytes_received (count)	Number of bytes received at the Oracle end of the connection. Shown as byte
oci.vpn.bytes_sent (count)	Number of bytes sent from the Oracle end of the connection. Shown as byte
oci.vpn.packets_error (count)	Number of packets dropped at the Oracle end of the connection. Dropped packets indicate a misconfiguration in some part of the overall system. Check if there's been a change to the configuration of your VCN, Site-to-Site VPN, or your CPE. Shown as packet
oci.vpn.packets_received (count)	Number of packets received at the Oracle end of the connection. Shown as packet
oci.vpn.packets_sent (count)	Number of packets sent from the Oracle end of the connection. Shown as packet
oci.vpn.tunnel_state (gauge)	Whether the tunnel is up (1) or down (0).
oci.waf.bandwidth (gauge)	Bandwidth rate calculated by dividing total data egress in a minute by 60. Shown as byte
oci.waf.number_of_requests (count)	The total number of requests serviced by the WAF. Shown as request
oci.waf.number_of_requests_detected (count)	The number of requests that triggered a detect (alert) for a WAF policy. Shown as request
oci.waf.traffic (gauge)	Data egress from the WAF (compressed by default) measured in one minute intervals. Shown as byte

Checks de servicio

La integración de OCI no incluye ningún check de servicio.

Eventos

La integración de OCI no incluye ningún evento.

Solucionar problemas

¿Necesitas ayuda? Ponte en contacto con el servicio de asistencia de Datadog.

Referencias adicionales

Más enlaces, artículos y documentación útiles:

Monitorizar Oracle Cloud Infrastructure con Datadog