Table: newrelic_notification_channel - Query New Relic Notification Channels using SQL
New Relic Notification Channels are part of the larger Alert system within New Relic, a cloud-based software to help website and application owners track the performances of their services. These channels represent the destinations for alerts generated by New Relic's monitoring services, such as email, Slack, or a custom webhook. They provide a way for New Relic to communicate alert information to users or systems.
Table Usage Guide
The newrelic_notification_channel
table provides insights into the notification channels within New Relic's Alert system. As a DevOps engineer, explore channel-specific details through this table, including type, configuration, and linked policies. Utilize it to manage and audit your alert communication settings, such as verifying the correct configuration of channels, understanding the distribution of alert types across channels, and ensuring the proper linkage to alert policies.
Important Notes
- You must specify the
account_id
in thewhere
clause to query this table.
Examples
List all notification channels for a specific account
Discover the segments that have active notifications for a specific user account. This can help in managing and organizing notifications, ensuring that important updates are not missed.
select id, name, account_id, active, created_at, updated_at, updated_by, destination_id, product, properties, status, typefrom newrelic_notification_channelwhere account_id = 21355;
select id, name, account_id, active, created_at, updated_at, updated_by, destination_id, product, properties, status, typefrom newrelic_notification_channelwhere account_id = 21355;
Schema for newrelic_notification_channel
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
account_id | bigint | = | ID of the account the channel belongs to. |
active | boolean | Indicates if the channel is enabled. | |
created_at | timestamp with time zone | Timestamp when the channel was created. | |
destination_id | text | The ID of the notification destination. | |
id | text | ID of the channel. | |
name | text | Name of the channel. | |
product | text | Name of the product the channel is created for. | |
profile_id | text | =, !=, ~~, ~~*, !~~, !~~* | Unique identifier of the current user. |
properties | jsonb | Array of properties associated with the channel. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
status | text | Status of the channel. | |
type | text | Type of the channel | |
updated_at | timestamp with time zone | Timestamp when channel was last updated. | |
updated_by | bigint | The 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_channel