1 of 1

New Relic

Create an outgoing webhook to send logs to New Relic triggered by Apono access request events

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

Item

Description

New Relic license location:

Creating the webhook

Follow these steps to configure a webhook:

On the Webhooks page, click Add Webhook. The Add Webhook page appears.
Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.
Click the Status toggle to Active.
From the Method dropdown menu, select POST.
In the URL field, enter https://log-api.newrelic.com/log/v1?Api-Key=<LICENSE_TOKEN>. Be sure to replace the <LICENSE_TOKEN> placeholder.

The webhook URL must adhere to the following requirements:

Uses the HTTPS protocol
Does not specify any custom ports

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}} "
}

Click View event's payload schema to reveal the payload schema and available data fields. You can also refer to the Webhook Payload Schema Reference to read the descriptions of each data field.

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
Under Filters, define one or several filter from the listed dropdown menus.

Filters empower admins to control the data transmitted via webhooks, minimizing the amount of data third-party tools receive and reducing unnecessary clutter.

Examples:

Send only production requests to your admins' Slack channel.
Trigger Okta workflows for events from specific integrations or resource types.
Open a ticket in Jira or ServiceNow for manually approved requests.

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.

For more information about the test, click View Invocation Data. A panel opens revealing the request, response, and other relevant details.

Should your test fail, view these tips to troubleshoot your webhook.

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:

New Relic

Create an outgoing webhook to send logs to New Relic triggered by Apono access request events

Prerequisite

Item

Description

New Relic license location:

Creating the webhook

Follow these steps to configure a webhook:

On the Webhooks page, click Add Webhook. The Add Webhook page appears.
Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.
Click the Status toggle to Active.
From the Method dropdown menu, select POST.
In the URL field, enter https://log-api.newrelic.com/log/v1?Api-Key=<LICENSE_TOKEN>. Be sure to replace the <LICENSE_TOKEN> placeholder.

The webhook URL must adhere to the following requirements:

Uses the HTTPS protocol
Does not specify any custom ports

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}} "
}

Click View event's payload schema to reveal the payload schema and available data fields. You can also refer to the Webhook Payload Schema Reference to read the descriptions of each data field.

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
Under Filters, define one or several filter from the listed dropdown menus.

Filters empower admins to control the data transmitted via webhooks, minimizing the amount of data third-party tools receive and reducing unnecessary clutter.

Examples:

Send only production requests to your admins' Slack channel.
Trigger Okta workflows for events from specific integrations or resource types.
Open a ticket in Jira or ServiceNow for manually approved requests.

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.

For more information about the test, click View Invocation Data. A panel opens revealing the request, response, and other relevant details.

Should your test fail, view these tips to troubleshoot your webhook.

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: