Moogsoft Docs

New Relic Insights Polling

You can install the New Relic Insights Polling integration to enable Moogsoft AIOps to collect event data from one or more New Relic Insights systems. The integration uses API authorization keys to authenticate with New Relic Insights.

See the New Relic documentation for details on New Relic Insights.

Before You Begin

The New Relic Insights Polling integration has been validated with New Relic Insights v2.3. Before you start to set up your integration, ensure you have met the following requirements for each New Relic system:

  • You have the New Relic Insights server URL.

  • You have the New Relic Insights Account ID and API Query Key.

  • Your New Relic Insights server is able to accept HTTP/HTTPS requests.

Configure the New Relic Insights Polling Integration

To configure the New Relic Insights Polling integration:

  1. Navigate to the Integrations tab.

  2. Click New Relic Insights (Polling) in the Monitoring section.

  3. Provide a unique integration name. You can use the default name or customize the name according to your needs.

  4. Provide connection details for your New Relic system.

Additionally, you can provide optional configuration details. See the New Relic Insights Reference for a description of all properties.

Configure New Relic Insights

Configure a webhook to push incidents from New Relic to New Relic Insights as follows. For more help, see the New Relic Documentation.

  1. Create a new notification channel in New Relic with the following properties:

    Field

    Value

    Channel Type

    Webhook

    Channel Name

    Send to New Relic Insights for Moogsoft AIOps

    Base URL

    Provide the New Relic Insights URL, for example:

    https://insights-collector.newrelic.com/v1/accounts/<account id>/events

  2. Add the following custom JSON payload:

    {
        "eventType":"Aiops_Incident",
        "account_id": "$ACCOUNT_ID",
        "account_name": "$ACCOUNT_NAME",
        "condition_id": "$CONDITION_ID",
        "condition_name": "$CONDITION_NAME",
        "current_state": "$EVENT_STATE",
        "details": "$EVENT_DETAILS",
        "event_type": "$EVENT_TYPE",
        "incident_acknowledge_url": "$INCIDENT_ACKNOWLEDGE_URL",
        "incident_id": "$INCIDENT_ID",
        "incident_url": "$INCIDENT_URL",
        "owner": "$EVENT_OWNER",
        "policy_name": "$POLICY_NAME",
        "policy_url": "$POLICY_URL",
        "runbook_url": "$RUNBOOK_URL",
        "severity": "$SEVERITY",
        "targets": "$TARGETS",
        "timestamp": "$TIMESTAMP",
        "violation_chart_url": "$VIOLATION_CHART_URL"
    }
  3. To include headers with webhooks, add Custom Headers and provide a name and value for each header.

    Name

    Value

    X-Insert-Key

    The Insights Insert Key

  4. Optionally send a test notification to verify that Moogsoft AIOps can receive a test event from New Relic Insights.

  5. Assign the notification channel to one or more alert policies in New Relic Insights. You can create a new alert policy or add the notification to an existing alert policy.

After you configure the integration, it polls your New Relic Insights servers at regular intervals to collect event data (every 60 seconds by default).

If the integration fails to connect to one or more New Relic Insights sources, Moogsoft AIOps creates an alert and writes the details to the process log. Refer to the logging details for LAMs and integrations for more information.