Datadog monitors your servers, databases, tools, and services, through a SaaS-based data analytics platform.

This guide shows you how to configure and test outbound webhooks for Datadog.

Prerequisite

Configure a webhook

Follow these steps to configure a webhook:

1. On the Webhooks page, click Add Webhook. The Add Webhook page appears.

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. For the webhook URL, enter https://<DATADOG_LOG_COLLECTOR_URL>/api/v2/logs. Be sure to replace <DATADOG_LOG_COLLECTOR_URL> with your Datadog organization location. For example, for the US5 region, enter: https://http-intake.logs.us5.datadoghq.com

1. In the Body Template field, paste the following JSON body for the webhook payload. Replace LOGS_TAGS with a comma-separated list of tags you want to associate with your logs. For example env:staging,version:5.1.

[
 {
   "ddsource": "apono",
   "ddtags": "<LOGS_TAGS>",
   "hostname": "apono",
   "message": "{ \"event_type\": \"{{ event_type }}\", \"event_time\": \"{{ event_time }}\", \"id\": \"{{ data.id }}\", \"friendly_id\": \"{{ data.friendly_id }}\", \"requester_id\": \"{{ data.requester.id }}\", \"requester_name\": \"{{ data.requester.name }}\", \"requester_email\": \"{{ data.requester.email }}\", \"justification\": \"{{ data.justification }}\", \"creation_date\": \"{{ data.creation_date }}\", \"access_flow_id\": \"{{ data.access_flow.id }}\", \"access_flow_name\": \"{{ data.access_flow.name }}\", \"access_bundle_id\": \"{{ data.access_bundle.id }}\", \"access_bundle_name\": \"{{ data.access_bundle.id }}\", \"access_groups_integration_name\": \"{{ data.access_groups.[0].integration.name }}\", \"access_groups_integration_type\": \"{{ data.access_groups.[0].integration.type }}\"}",
   "alert_type": "info",
   "service": "apono"
 }
]

1. For Headers, enter the following authorization headers. Replace the placeholder values with the API key and key ID that you created in Datadog.

1. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • Created

   • Approved

   • Rejected

   • Granted

   • Expired

   • Failed

2. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request logs will be sent to Datadog based on the triggers you have selected.

SolarWinds' flagship product, Orion platform, is a comprehensive network management solution offering real-time monitoring and performance optimization for IT infrastructures. It enables IT professionals to quickly identify and resolve issues, optimize resource utilization, and ensure smooth network operation.

Prerequisites

Configure a webhook

Follow these steps to configure a webhook:

1. On the Webhooks page, click Add Webhook. The Add Webhook page appears.

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. In the URL field, enter the data source endpoint.

1. In the Body Template field, construct a JSON body for the webhook payload.

{
   "apono_event":"{{event_type}} request event from Apono made by {{data.requester.name}} - {{data.requester.email}}"
}

1. Under Headers, use the following Key and Value to set the headers. Be sure to replace the <TOKEN> and <X-OTEL-RESOURCE-ATTR> placeholders.

1. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • RequestCreated

   • RequestApproved

   • RequestRejected

   • RequestGranted

   • RequestExpired

   • RequestFailed

   • Manual

2. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request logs will be sent to SolarWinds based on the triggers you have selected.

Results

Your webhook should now start sending logs in the webhook SolarWinds account once triggered:

New Relic browser monitoring helps you understand website performance and user behavior by monitoring real user data. It tracks page load times, network requests, JavaScript errors, user interactions, and more. Analyzing navigation timing helps you find issues that hurt your web app's performance or backend errors.

Prerequisite

New Relic license location:

Creating the webhook

Follow these steps to configure a webhook:

1. On the Webhooks page, click Add Webhook. The Add Webhook page appears.

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. In the URL field, enter https://log-api.newrelic.com/log/v1?Api-Key=<LICENSE_TOKEN>. Be sure to replace the <LICENSE_TOKEN> placeholder.

1. In the Body Template field, construct a JSON body for the webhook payload.

{
"timestamp": {{event_time}},
"attributes": {
   "error.message": "New {{event_type}} by {{data.requester.name}} - {{data.requester.email}}",
   "user.id": "{{data.requester.id}}",
   "transaction.id": "{{event_type}}"
},
"message": "New {{event_type}} by {{data.requester.name}}/{{data.requester.id}} - {{data.requester.email}}, for {{data.access_groups.integration.name}} - {{data.access_groups.resource_types.name}} "
}

1. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • RequestCreated

   • RequestApproved

   • RequestRejected

   • RequestGranted

   • RequestExpired

   • RequestFailed

   • Manual

2. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request logs will be sent to New Relic based on the triggers you have selected.

Results

Your webhook should now start sending logs to New Relic in the relevant account once triggered:

Splunk is software used to search and analyze machine data. This machine data can come from web applications, sensors, devices or any data created by user. It serves the needs of IT infrastructure by analyzing the logs generated in various processes.

Prerequisite

• . Copy the token to use it later.\

Configure a webhook

Follow these steps to configure a webhook:

1. On the page, click Add Webhook. The Add Webhook page appears.

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. For the webhook URL, enter https://<host>:<port>/services/collector.

6. In the Body Template field, construct a JSON body for the webhook payload.

1. For Headers, enter the following authorization headers: Authorization: Bearer <TOKEN>

2. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • Created

   • Approved

   • Rejected

   • Granted

   • Expired

   • Failed

3. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request events will be sent Splunk based on the triggers you have selected.

Sumo Logic is a cloud-native secure, centralized log analytics service that provides insights into logs through pre-built applications, identifying patterns to show outliers in the behaviors of applications and systems.

This guide shows you how to configure and test outbound webhooks for Sumo Logic.

Prerequisite

• and copy the access key to use it later

• for Apono app and copy the HTTP Source Address you get after saving the new collection

  • Set Message Processing to One Message Per Request:

• Copy Apono app

Configure a webhook

Follow these steps to configure a webhook:

1. On the page, click Add Webhook. The Add Webhook page appears.

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. For the webhook URL, enter the HTTP Source Address.

6. In the Body Template field, paste the for the webhook payload.

2. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • Created

   • Approved

   • Rejected

   • Granted

   • Expired

   • Failed

3. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request logs will be sent to Sumo Logic based on the triggers you have selected.

Results

Your webhook should now start sending new logs to Sumo Logic once triggered:

Grafana allows you to query, visualize, alert on, and understand your metrics no matter where they are stored. Create, explore, and share dashboards with your team and foster a data-driven culture.

Prerequisite

Creating the webhook

Follow these steps to configure an Apono webhook:

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. In the URL field, enter https://<INCOMING_WEBHOOK_URL>?title=json(title). Be sure to replace the <INCOMING_WEBHOOK_URL> placeholder.

1. In the Body Template field, construct a JSON body for the webhook payload.

1. Under Headers, use the following Key and Value to set the header. Be sure to replace the <INCOMING_WEBHOOK_TOKEN> placeholder.

1. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • RequestCreated

   • RequestApproved

   • RequestRejected

   • RequestGranted

   • RequestExpired

   • RequestFailed

   • Manual

2. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request logs will be sent to Grafana based on the triggers you have selected.

Results

Your webhook should now start creating new incidents to Grafana once triggered:

Logpoint collects real-time data from multiple sources and centralizes it for comprehensive analysis. You can search, analyze, generate reports, detect vulnerabilities, and configure alerts to enhance threat detection capabilities. You can also automate threat response based on specific security incidents.

Prerequisite

• two request parameters:

  • username, which includes a Logpoint username. Your access control for using the APIs is the same as your user roles in the system

  • secret_key, which is the access key to uniquely identify you as an authorized user.

    \

Configure a webhook

Follow these steps to configure a webhook:

1. On the page, click Add Webhook. The Add Webhook page appears.

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. For the webhook URL, enter https://Logpoint-IP/reopen_incident.

6. In the Body Template field, construct a JSON body for the webhook payload.

1. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • Created

   • Approved

   • Rejected

   • Granted

   • Expired

   • Failed

2. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request incident will be created on Logpoint based on the triggers you have selected.

Logz.io collects and analyze logs, metrics, and traces, combined with human-powered AI/ML features through a SaaS-based data analytics platform.

Prerequisite

Logz.io Listener URL location:

Creating the webhook

Follow these steps to configure an Apono webhook:

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. In the URL field, enter https://<LISTENER_URL>?token=<LOG_SHIPPING_TOKEN>. Be sure to replace the <LISTENER_URL> and <LOG_SHIPPING_TOKEN> placeholders.

1. In the Body Template field, construct a JSON body for the webhook payload.

1. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • RequestCreated

   • RequestApproved

   • RequestRejected

   • RequestGranted

   • RequestExpired

   • RequestFailed

   • Manual

2. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request logs will be sent to Logz.io based on the triggers you have selected.

Results

Your webhook should now start sending logs to Logz.io in the relevant account once triggered:

Coralogix is a log analytics platform that uses machine learning and real-time streaming to provide insights into log data, helping with monitoring, troubleshooting, and optimization. It offers features like dynamic data parsing, alerting, and anomaly detection, allowing teams to efficiently manage and analyze large volumes of log data. Coralogix is known for its scalability and robust analytics capabilities.

Prerequisite

Creating the webhook

Follow these steps to configure a webhook:

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. In the URL field, enter https://<GENERATED_INCOMING_WEBHOOK_URL>. Be sure to replace <GENERATED_INCOMING_WEBHOOK_URL> with the Coralogix incoming webhook URL.

1. In the Body Template field, construct a JSON body for the webhook payload.

1. Under Headers, use the following Key and Value to set the header. Be sure to replace <API_KEY> with the Coralogix API key.

1. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • RequestCreated

   • RequestApproved

   • RequestRejected

   • RequestGranted

   • RequestExpired

   • RequestFailed

   • Manual

2. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request logs will be sent to Coralogix based on the triggers you have selected.

Results

Your webhook should now start sending new logs to Coralogix once triggered:

Microsoft Sentinel is a scalable, cloud-native security information and event management (SIEM) that delivers an intelligent and comprehensive solution for SIEM and security orchestration, automation, and response (SOAR). Microsoft Sentinel provides cyberthreat detection, investigation, response, and proactive hunting, with a bird's-eye view across your enterprise.

Prerequisite

• Configure logs ingestion API in Azure Monitor to send Apono's access request events data to a Log Analytics workspace with a REST API by using the following guide.

  • You can use the following sample JSON as the table schema file on the parse and filter sample data step:

[
  {
    "event_type": "string",
    "requester_id": "string",
    "requester_name": "string",
    "requester_email": "string",
    "justification": "string",
    "resource_id": "string",
    "resource_name": "string",
    "permission": "string"
  }
]

• Azure JWT token.

  • Get your JWT token using Postman:

    • Set up the Token Request:

      • Method: POST

      • URL: https://login.microsoftonline.com/<TenantId>/oauth2/v2.0/token Replace TenantId with your Azure AD Tenant ID.

    • Add the Body parameters:

      • Go to the Body tab and select x-www-form-urlencoded.

        • Add the following key-value pairs:

          • grant_type: client_credentials

          • client_id: Your application's Client ID.

          • client_secret: Your application's Client Secret.

          • scope: https://monitor.azure.com/.default The scope should target the Azure Monitor API, represented by https://monitor.azure.com/.default.

      • Send the Request:

        • Click Send and copy the access_token value. If the credentials are correct, you will receive a response similar to this:

{
  "token_type": "Bearer",
  "expires_in": 3600,
  "ext_expires_in": 3600,
  "access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJI..."
}

• Microsoft incident creation rule in your Sentinel Analytics.

  • Microsoft incident creation rule example:

    • Under General set the following:

      • Severity: Information

      • MITRE ATT&CK: T1650 - Acquire Access

    • Under Set rule logic set the following:

      • Rule query: <Log-Analytics-table-name>

Configure a webhook

Follow these steps to configure a webhook:

1. On the Webhooks page, click Add Webhook. The Add Webhook page appears.

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. For the webhook URL, enter <Data Collection Endpoint URI>/dataCollectionRules/<DCR Immutable ID>/streams/<Stream Name>?api-version=2023-01-01.

6. In the Body Template field, construct a JSON body for the webhook payload.

   Copy

   [
     {
       "TimeGenerated": "{{event_time}}",
       "event_type": "{{event_type}}",
       "requester_id": "{{data.requester.id}}",
       "requester_name": "{{data.requester.name}}",
       "requester_email": "{{data.requester.email}}",
       "justification": "{{data.justification}}",
       "resource_id": "{{data.access_groups.[0].access_units.[0].resource.type.name}}",
       "resource_name": "{{data.access_groups.[0].access_units.[0].resource.name}}",
       "permission":  "{{data.access_groups.[0].access_units.[0].permission.name}}"
     }
   ]

1. For Headers, enter the following authorization headers: Authorization: Bearer <JWT-TOKEN>.

2. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • Created

   • Approved

   • Rejected

   • Granted

   • Expired

   • Failed

3. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request incident will be created on Sentinel based on the triggers you have selected.

Results

Your webhook should now start creating new incidents on Sentinel once triggered:

Cortex makes it easy for engineering organizations to gain visibility into their services and deliver high quality software.

This guide shows you how to configure and test outbound webhooks for Cortex.

Prerequisite

• Cortex API key and assigned User role to it. Copy the API key to use it later.

• Cortex entity. Use Create an entity manually for Apono access request events.

Configure a webhook

Follow these steps to configure a webhook:

1. On the Webhooks page, click Add Webhook. The Add Webhook page appears.

2. Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.

3. Click the Status toggle to Active.

4. From the Method dropdown menu, select POST.

5. For the webhook URL, enter https://api.getcortexapp.com/api/v1/catalog/<entity-tagOrId>/custom-events.

6. In the Body Template field, construct a JSON body for the webhook payload.

   Copy

   {
     "customData": {...},
     "description": "New {{event_type}} request made by {{data.requester.name}}",
     "timestamp": "{{event_time}}",
     "title": "New {{event_type}} request made by {{data.requester.name}}",
     "type": "{{event_type}}"
   }

1. For Headers, enter the following authorization headers: Authorization: Bearer <BASE64-API-KEY>

2. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

   • Created

   • Approved

   • Rejected

   • Granted

   • Expired

   • Failed

3. Under Filters, define one or several filter from the listed dropdown menus.

1. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request custom event will be created on Cortex Apono entity based on the triggers you have selected.