New Relic

Freesbe takes alert issues from New Relic. Once an admin connects it:

• Each issue posts into the channel you pick as one card, with its priority, title, the entities it’s about, the condition that opened it and the policy.
• The same card stays current. When the issue is acknowledged in New Relic, the card says so, and when it closes, the card turns green and says how long it was open, with a reply under it for everyone following the thread.
• Acknowledge and Resolve on the card change the issue in New Relic, when you give Freesbe your account ID and a user key.
• A live problems board pinned in the channel lists every issue open right now, worst first, and reports post on their own every morning or every Monday.

Issues post as their own member, New Relic, so their cards are easy to tell apart from people.

Connect New Relic

Only owners and admins can connect it. You need someone who can manage alert workflows in New Relic.

1. Open Workspace settings → Integrations & apps → Integrations → Monitoring and click Connect under New Relic.
2. Give the connection a name, like New Relic: production, and pick the channel it posts to.
3. Pick which issues to post under Issues to post (see Priorities).
4. For the Acknowledge and Resolve buttons, fill in New Relic address and API token (see Acknowledge and resolve from the card). You can add them later.
5. Click Connect New Relic. Freesbe shows the Freesbe URL and the Payload for New Relic. Copy the URL now: it’s only shown once.

Then, in New Relic:

1. Open Alerts → Destinations and add a Webhook. Name it Freesbe and paste the Freesbe URL in Endpoint URL. Save it.
2. Open Alerts → Workflows, pick or add the workflow for the issues that should post, and add the Freesbe webhook as a channel.
3. Replace the channel’s payload with the one Freesbe showed you, keep notifications for acknowledged and closed issues on, and save the workflow. Send test notification posts a card right away.

The payload is the same for every connection:

{ "id":
{{json issueId}}, "url":
{{json issuePageUrl}}, "title":
{{json annotations.title.[0]}}, "priority":
{{json priority}}, "state":
{{json state}}, "entities":
{{json entitiesData.names}}, "conditions":
{{json accumulations.conditionName}}, "policies":
{{json accumulations.policyName}}, "createdAt":
{{createdAt}}, "updatedAt":
{{updatedAt}}
}

Priorities

Freesbe goes by the issue’s priority:

In New Relic	On the card	Icon
Critical	Critical	🚨
High	High	🔴
Medium	Minor	🟠
Low	Warning	🟡

Issues to post leaves out issues below the priority you pick. An issue whose priority changes changes the same card.

Acknowledge and resolve from the card

With a key, everyone in the channel can press Acknowledge and Resolve on an open issue’s card. The card shows who pressed it. New Relic records the change as the person whose key it is, so a key made for Freesbe, or a shared on-call user’s, reads best there.

To set it up:

1. In New Relic, open API keys (from your name, bottom left), and create a User key (NRAK-…) for the account the alerts are in.
2. Copy the account ID from the same page.
3. In the connection’s settings in Freesbe, fill in New Relic address with where you open New Relic (https://one.newrelic.com, or https://one.eu.newrelic.com for an EU account), and in API token paste the account ID and the key with a colon between them: 1234567:NRAK-….

Freesbe checks the key can see the account before saving it, and keeps it encrypted.

The board and reports

Like Zabbix, each connection pins a live problems board in its channel, listing the issues open right now, worst first, with how long and whether they’re acknowledged. Reports count the issues Freesbe got over the last day or week: by priority, still open, total time, the typical time to close, the noisiest conditions and the busiest entities. See The live problems board and Reports for more.

Questions

Can different issues go to different channels? Yes. Connect New Relic once per channel, with a destination for each, and add each one to the workflows whose issues belong there.

Who can see the cards? Everyone in the channel. Use a private channel for issues only some people should see.

Is the URL a secret? Yes: anyone with it can post issues into the channel. If it leaks, delete the connection and connect again for a new URL.