Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Overview
Oracle Cloud Infrastructure (OCI) Oracle Integration is a robust business automation platform with a comprehensive portfolio of integration and automation capabilities, enabling you to connect applications and data, automate business processes, and innovate with AI, all in a fully managed, preconfigured environment.
This integration helps you detect anomalies and bottlenecks occurring within your Oracle Integration instances and connected applications by collecting metrics from the oci_integration namespace.
Setup
Installation
After setting up the Oracle Cloud Infrastructure integration, ensure that any namespaces mentioned in the Overview are included in your Connector Hub.
Data Collected
Metrics
| |
|---|
oci.integration.billed_message_count
(count) | Number of billing messages that the service instance used for incoming and outgoing messages for trigger and invoke requests.
Shown as message |
oci.integration.billed_message_count_data_retention
(count) | Number of billing messages used for extended data retention.
Shown as message |
oci.integration.billed_message_pack_count
(count) | Number of message packs that you purchased.
Shown as message |
oci.integration.configured_messages
(count) | Number of billing messages that were configured.
Shown as message |
oci.integration.inbound_request_processing_time
(gauge) | The time taken for processing inbound requests. In case of synchronous requests, it is the total time taken for processing a request and sending the response. In case of fire-and-forget inbound requests, it is the time taken to persist the request and send the acknowledgment. This metric captures the time elapsed (in milliseconds) by the trigger in processing the incoming request.
Shown as millisecond |
oci.integration.messages_failed_count
(count) | Number of messages that could not be processed. For example, a message can’t be processed when an external endpoint that is used in an integration goes down.
Shown as message |
oci.integration.messages_received_count
(count) | Number of messages that were received. This count doesn’t indicate whether the messages processed successfully.
Shown as message |
oci.integration.messages_successful_count
(count) | Number of messages that were processed successfully.
Shown as message |
oci.integration.number_of_outbound_requests
(count) | Number of requests received by Oracle Integration using any adapter-specific trigger connection. This metric includes the HTTPs requests posted to Oracle Integration and the messages polled by adapters such as Oracle Advanced Queuing (AQ) Adapter, IBM MQ Series JMS Adapter, Apache Kafka Adapter, Oracle Database Adapter, and so on.
Shown as request |
oci.integration.number_of_inbound_requests
(count) | Number of outbound requests sent by the adapter as part of the invoke activity in Oracle Integration.
Shown as request |
oci.integration.opabilled_decision_message_count
(count) | Number of billing messages that decisions used.
Shown as message |
oci.integration.opabilled_process_message_count
(count) | Number of process billing messages that Process Automation used.
Shown as message |
oci.integration.outbound_request_invocation_time
(gauge) | Time (in milliseconds) spent by the adapter during the invocation of the target endpoint.
Shown as millisecond |
oci.integration.rpabilled_message_count
(count) | Number of billing messages that robotic process automation used.
Shown as message |
oci.integration.total_billed_message_count
(count) | Total number of billing messages used by all components except Visual Builder. This total doesn’t include disaster recovery.
Shown as message |
Service Checks
OCI Integrations does not include any service checks.
Events
OCI Integrations does not include any events.
Troubleshooting
Need help? Contact Datadog support.
