Table: newrelic_alert_channel - Query New Relic Alert Channels using SQL
New Relic Alert Channels are part of the New Relic Alerts service that helps you monitor and respond to changes in your system. It provides a centralized way to manage alert notifications for various resources, enabling rapid response to system issues. Alert Channels allow you to define where and how you want to receive alert notifications.
Table Usage Guide
The newrelic_alert_channel
table provides insights into alert channels within New Relic Alerts service. As a DevOps engineer, explore channel-specific details through this table, including configuration, status, and associated metadata. Utilize it to manage and monitor your alert channels, ensuring timely and appropriate notifications for system issues.
Examples
List all alert channels
Explore various alert channels to understand their types, recipients, associated teams, and other related details. This is useful in gaining insights into how alerts are managed and disseminated within your organization.
select id, name, type, channel, recipients, teams, tags, url, key, route_key, base_url, payload_type, region, user_id, policiesfrom newrelic_alert_channel;
select id, name, type, channel, recipients, teams, tags, url, key, route_key, base_url, payload_type, region, user_id, policiesfrom newrelic_alert_channel;
List all slack alert channels
Explore all the alert channels set up on Slack to gain insights into the distribution of alerts across different teams and regions. This can help in managing the alert system more efficiently and ensuring all relevant parties are notified.
select name, channel, recipients, region, teams, tagsfrom newrelic_alert_channelwhere type = 'slack';
select name, channel, recipients, region, teams, tagsfrom newrelic_alert_channelwhere type = 'slack';
Schema for newrelic_alert_channel
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form, e.g. connection_name. | |
base_url | text | The base URL associated with the alert channel. | |
channel | text | The channel associated with the alert channel. | |
id | bigint | = | Unique identifier for the alert channel. |
key | text | The key associated with the alert channel. | |
name | text | Name of the alert channel. | |
payload_type | text | The type of the payload sent to the alert channel. | |
policies | jsonb | An array of policy identifiers that link the alert channel to a policy. | |
recipients | text | The configured recipients of this alert channel. | |
region | text | The region in which the alert channel is configured. | |
route_key | text | The route key associated with the alert channel. | |
service_key | text | The service key associated with the alert channel. | |
tags | text | The tags associated with the alert channel. | |
teams | text | The configured teams associated with this alert channel. | |
type | text | The type of alert channel (slack, email, webhook, etc). | |
url | text | The URL associated with the alert channel. | |
user_id | text | The identifier of the user whom created the alert 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_alert_channel