# New Relic

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

<table><thead><tr><th width="296">Item</th><th>Description</th></tr></thead><tbody><tr><td><strong>Permissions</strong></td><td>Admin user for New Relic Admin account</td></tr><tr><td><strong>New Relic license token</strong></td><td>From New Relic Admin portal click on your <strong>user logo</strong> on the left navigator bottom and choose API Keys. find your <strong>License Key for Account &#x3C;YOUR_ACCOUNT_ID></strong>, from the ... click on <strong>Copy key</strong>.</td></tr></tbody></table>

New Relic license location:

![](https://files.readme.io/274fbad-image.png)

***

### Creating the webhook

Follow these steps to configure a webhook:

1. On the [**Webhooks**](https://app.apono.io/webhooks) page, click **Add Webhook**. The **Add Webhook** page appears.
2. Click **Request Webhook**.
3. Enter a unique, alphanumeric, user-friendly **Request Webhook Name** for identifying this webhook.
4. Click the **Status** toggle to **Active**.
5. From the **Method** dropdown menu, select **POST**.
6. In the **URL** field, enter *<https://log-api.newrelic.com/log/v1?Api-Key=\\>\<LICENSE\_TOKEN>*.\
   \
   Be sure to replace the `<LICENSE_TOKEN>` placeholder.

{% hint style="warning" %}
The webhook URL **must adhere** to the following requirements:

* Uses the HTTPS protocol
* Does **not** specify any custom ports
  {% endhint %}

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

{% code overflow="wrap" %}

```json
{
"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}} "
}
```

{% endcode %}

{% hint style="success" %}
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](https://docs.apono.io/docs/webhook-integrations/webhook-payload-references/webhook-payload-schema-reference) to read the descriptions of each data field.
{% endhint %}

8. From the **Triggers** dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:
   * **RequestCreated**
   * **RequestApproved**
   * **RequestExpired**
   * **RequestFailed**
   * **RequestGranted**
   * **RequestRejected**
9. Under **Filters**, define one or several filter from the listed dropdown menus.

{% hint style="info" %}
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.
  {% endhint %}

10. (Optional) In the **Timeout in seconds** field, enter the duration in seconds to wait before marking the request as failed.
11. (Optional) Define **Response Validators** to verify that the response from the webhook meets specified criteria:
    1. Click **+ Add**. A row of settings appears.
    2. Starting with *$.data.*, enter the **Json Path** of the JSON parameter.
    3. In the **Expected Values** field, enter a value and press the Enter key on your keyboard.
    4. Repeat step **c** to add several expected values.
    5. Repeat steps **a-d** to add multiple response validators.
12. 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.

{% hint style="success" %}
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](https://docs.apono.io/docs/webhook-integrations/troubleshoot-a-webhook).
{% endhint %}

13. 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:

![](https://files.readme.io/3b531b3-image.png)

![](https://files.readme.io/585d345-image.png)