turbot/newrelic
steampipe plugin install newrelic

Table: newrelic_notification_destination - Query New Relic Notification Destinations using SQL

New Relic Notification Destinations are channels configured in New Relic to receive notifications. These channels can be of different types like email, Slack, PagerDuty, etc. They are a crucial part of New Relic's Alert system, tying together the alert policies and the users who need to be notified.

Table Usage Guide

The newrelic_notification_destination table provides insights into the notification channels configured in New Relic. As a DevOps engineer, you can explore details about these channels, including their types and configurations, through this table. Utilize it to manage and optimize your alert system by understanding the distribution of notifications across different channels.

Important Notes

  • You must specify the account_id in the where clause to query this table.

Examples

List all notification destinations for a specific account

Determine the areas in which notifications are being sent for a specific user account. This can be useful to audit and manage where notifications are directed, ensuring the right individuals or teams are alerted.

select
id,
name,
account_id,
active,
created_at,
updated_at,
updated_by,
auth,
is_user_authenticated,
properties,
status,
type
from
newrelic_notification_destination
where
account_id = 21355;
select
id,
name,
account_id,
active,
created_at,
updated_at,
updated_by,
auth,
is_user_authenticated,
properties,
status,
type
from
newrelic_notification_destination
where
account_id = 21355;

Schema for newrelic_notification_destination

NameTypeOperatorsDescription
_ctxjsonbSteampipe context in JSON form.
account_idbigint=ID of the account the channel belongs to.
activebooleanIndicates if the destination is enabled.
authtextAuthentication type used for the destination.
created_attimestamp with time zoneTimestamp when the destination was created.
idtextID of the channel.
is_user_authenticatedbooleanIndicates if current user is authenticated with the destination.
last_senttimestamp with time zoneTimestamp when last notification was sent to destination.
nametextName of the destination.
profile_idtext=, !=, ~~, ~~*, !~~, !~~*Unique identifier of the current user.
propertiesjsonbArray of properties associated with the destination.
sp_connection_nametext=, !=, ~~, ~~*, !~~, !~~*Steampipe connection name.
sp_ctxjsonbSteampipe context in JSON form.
statustextStatus of the destination.
typetextType of the destination.
updated_attimestamp with time zoneTimestamp when destination was last updated.
updated_bybigintThe ID of the user which last updated the channel.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- newrelic

You can pass the configuration to the command with the --config argument:

steampipe_export_newrelic --config '<your_config>' newrelic_notification_destination