Oracle Enterprise Manager (OEM) Integration webhook test alarms shows as successful, but no alarms

Products

• DX SaaS

Issue/Introduction

Users may observe that webhooks from Oracle Enterprise Manager (OEM) or other third-party sources report a "Successful" status at the source, but no alarms, metrics, or events appear in the DX Operational Intelligence (DX OI) / DX Operational Observability (DX O2) tenant. 

Reviewing the source logs (e.g., emoms.trc logs) reveals messages such as:
`Webhook REST call returned an unsuccessful status: 401`

Environment

*   DX Operational Observability (DX O2) SaaS
*   Open Data Connector (ODC)
*   Oracle Enterprise Manager (OEM) Integration

Cause

The issue is typically caused by a configuration conflict in the webhook's authentication settings. Specifically, the webhook is configured with a standard **Authentication Type** (such as **Basic**) while simultaneously including a manual **Authorization HTTP Header** containing a token. 

The DX SaaS ODC endpoint cannot process both authentication methods in a single request, leading to an authentication failure and a HTTP 401 Unauthorized response.

Resolution

To resolve this conflict, modify the webhook configuration at the source system (e.g., OEM):

1.  **Modify Authentication Settings:**
    *   Set the **Authentication Type** to **None** (or "No Authentication").
    *   Retain the manual **HTTP Header** for **Authorization** containing the required tenant token.
2.  **Verify Token Validity:**
    *   Ensure the token used in the header is active and has not expired.
    *   If necessary, generate a new token from the DX SaaS **Settings > Secure Tokens** menu.
3.  **Test the Webhook:**
    *   Trigger a test alarm from the source system.
    *   Verify that the ingestion traffic is visible in the `odc-connector` or `odc-controller` logs.
    *   Confirm the alarm appears in the tenant's Alarm Console.