newrelic.NrqlAlertCondition

A NRQL query. See NRQL below for details.

The ID of the policy where this condition should be used.

The New Relic account ID of the account you wish to create the condition. Defaults to the account ID set in your environment variable NEW_RELIC_ACCOUNT_ID.

How long we wait for data that belongs in each aggregation window. Depending on your data, a longer delay may increase accuracy but delay notifications. Use aggregation_delay with the event_flow and cadence methods. The maximum delay is 1200 seconds (20 minutes) when using event_flow and 3600 seconds (60 minutes) when using cadence. In both cases, the minimum delay is 0 seconds and the default is 120 seconds. aggregation_delay cannot be set with nrql.evaluation_offset.

Determines when we consider an aggregation window to be complete so that we can evaluate the signal for incidents. Possible values are cadence, event_flow or event_timer. Default is event_flow. aggregation_method cannot be set with nrql.evaluation_offset.

How long we wait after each data point arrives to make sure we've processed the whole batch. Use aggregation_timer with the event_timer method. The timer value can range from 0 seconds to 1200 seconds (20 minutes); the default is 60 seconds. aggregation_timer cannot be set with nrql.evaluation_offset.

The duration of the time window used to evaluate the NRQL query, in seconds. The value must be at least 30 seconds, and no more than 900 seconds (15 minutes). Default is 60 seconds.

The baseline direction of a baseline NRQL alert condition. Valid values are: lower_only, upper_and_lower, upper_only (case insensitive).

Whether to close all open incidents when the signal expires.

A list containing the critical threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

The description of the NRQL alert condition.

Whether to enable the alert condition. Valid values are true and false. Defaults to true.

How long we wait until the signal starts evaluating. The maximum delay is 7200 seconds (120 minutes).

The amount of time (in seconds) to wait before considering the signal expired. The value must be at least 30 seconds, and no more than 172800 seconds (48 hours).

Which strategy to use when filling gaps in the signal. Possible values are none, last_value or static. If static, the fill_value field will be used for filling gaps in the signal.

This value will be used for filling gaps in the signal.

The title of the condition.

Whether to create a new incident to capture that the signal expired.

Runbook URL to display in notifications.

Gathers data in overlapping time windows to smooth the chart line, making it easier to spot trends. The slide_by value is specified in seconds and must be smaller than and a factor of the aggregation_window.

DEPRECATED Use critical, and warning instead. A list of terms for this condition. See Terms below for details.

Deprecated:

use critical and warning attributes instead

The type of the condition. Valid values are static or baseline. Defaults to static.

DEPRECATED: Use violation_time_limit_seconds instead. Sets a time limit, in hours, that will automatically force-close a long-lasting incident after the time limit you select. Possible values are ONE_HOUR, TWO_HOURS, FOUR_HOURS, EIGHT_HOURS, TWELVE_HOURS, TWENTY_FOUR_HOURS, THIRTY_DAYS (case insensitive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

Deprecated:

use violation_time_limit_seconds attribute instead

Sets a time limit, in seconds, that will automatically force-close a long-lasting incident after the time limit you select. The value must be between 300 seconds (5 minutes) to 2592000 seconds (30 days) (inclusive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

A list containing the warning threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

A NRQL query. See NRQL below for details.

The ID of the policy where this condition should be used.

The New Relic account ID of the account you wish to create the condition. Defaults to the account ID set in your environment variable NEW_RELIC_ACCOUNT_ID.

How long we wait for data that belongs in each aggregation window. Depending on your data, a longer delay may increase accuracy but delay notifications. Use aggregation_delay with the event_flow and cadence methods. The maximum delay is 1200 seconds (20 minutes) when using event_flow and 3600 seconds (60 minutes) when using cadence. In both cases, the minimum delay is 0 seconds and the default is 120 seconds. aggregation_delay cannot be set with nrql.evaluation_offset.

Determines when we consider an aggregation window to be complete so that we can evaluate the signal for incidents. Possible values are cadence, event_flow or event_timer. Default is event_flow. aggregation_method cannot be set with nrql.evaluation_offset.

How long we wait after each data point arrives to make sure we've processed the whole batch. Use aggregation_timer with the event_timer method. The timer value can range from 0 seconds to 1200 seconds (20 minutes); the default is 60 seconds. aggregation_timer cannot be set with nrql.evaluation_offset.

The duration of the time window used to evaluate the NRQL query, in seconds. The value must be at least 30 seconds, and no more than 900 seconds (15 minutes). Default is 60 seconds.

The baseline direction of a baseline NRQL alert condition. Valid values are: lower_only, upper_and_lower, upper_only (case insensitive).

Whether to close all open incidents when the signal expires.

A list containing the critical threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

The description of the NRQL alert condition.

Whether to enable the alert condition. Valid values are true and false. Defaults to true.

How long we wait until the signal starts evaluating. The maximum delay is 7200 seconds (120 minutes).

The amount of time (in seconds) to wait before considering the signal expired. The value must be at least 30 seconds, and no more than 172800 seconds (48 hours).

Which strategy to use when filling gaps in the signal. Possible values are none, last_value or static. If static, the fill_value field will be used for filling gaps in the signal.

This value will be used for filling gaps in the signal.

The title of the condition.

Whether to create a new incident to capture that the signal expired.

Runbook URL to display in notifications.

Gathers data in overlapping time windows to smooth the chart line, making it easier to spot trends. The slide_by value is specified in seconds and must be smaller than and a factor of the aggregation_window.

DEPRECATED Use critical, and warning instead. A list of terms for this condition. See Terms below for details.

Deprecated:

use critical and warning attributes instead

The type of the condition. Valid values are static or baseline. Defaults to static.

DEPRECATED: Use violation_time_limit_seconds instead. Sets a time limit, in hours, that will automatically force-close a long-lasting incident after the time limit you select. Possible values are ONE_HOUR, TWO_HOURS, FOUR_HOURS, EIGHT_HOURS, TWELVE_HOURS, TWENTY_FOUR_HOURS, THIRTY_DAYS (case insensitive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

Deprecated:

use violation_time_limit_seconds attribute instead

Sets a time limit, in seconds, that will automatically force-close a long-lasting incident after the time limit you select. The value must be between 300 seconds (5 minutes) to 2592000 seconds (30 days) (inclusive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

A list containing the warning threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

A NRQL query. See NRQL below for details.

The ID of the policy where this condition should be used.

The New Relic account ID of the account you wish to create the condition. Defaults to the account ID set in your environment variable NEW_RELIC_ACCOUNT_ID.

How long we wait for data that belongs in each aggregation window. Depending on your data, a longer delay may increase accuracy but delay notifications. Use aggregation_delay with the event_flow and cadence methods. The maximum delay is 1200 seconds (20 minutes) when using event_flow and 3600 seconds (60 minutes) when using cadence. In both cases, the minimum delay is 0 seconds and the default is 120 seconds. aggregation_delay cannot be set with nrql.evaluation_offset.

Determines when we consider an aggregation window to be complete so that we can evaluate the signal for incidents. Possible values are cadence, event_flow or event_timer. Default is event_flow. aggregation_method cannot be set with nrql.evaluation_offset.

How long we wait after each data point arrives to make sure we've processed the whole batch. Use aggregation_timer with the event_timer method. The timer value can range from 0 seconds to 1200 seconds (20 minutes); the default is 60 seconds. aggregation_timer cannot be set with nrql.evaluation_offset.

The duration of the time window used to evaluate the NRQL query, in seconds. The value must be at least 30 seconds, and no more than 900 seconds (15 minutes). Default is 60 seconds.

The baseline direction of a baseline NRQL alert condition. Valid values are: lower_only, upper_and_lower, upper_only (case insensitive).

Whether to close all open incidents when the signal expires.

A list containing the critical threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

The description of the NRQL alert condition.

Whether to enable the alert condition. Valid values are true and false. Defaults to true.

How long we wait until the signal starts evaluating. The maximum delay is 7200 seconds (120 minutes).

The amount of time (in seconds) to wait before considering the signal expired. The value must be at least 30 seconds, and no more than 172800 seconds (48 hours).

Which strategy to use when filling gaps in the signal. Possible values are none, last_value or static. If static, the fill_value field will be used for filling gaps in the signal.

This value will be used for filling gaps in the signal.

The title of the condition.

Whether to create a new incident to capture that the signal expired.

Runbook URL to display in notifications.

Gathers data in overlapping time windows to smooth the chart line, making it easier to spot trends. The slide_by value is specified in seconds and must be smaller than and a factor of the aggregation_window.

DEPRECATED Use critical, and warning instead. A list of terms for this condition. See Terms below for details.

Deprecated:

use critical and warning attributes instead

The type of the condition. Valid values are static or baseline. Defaults to static.

DEPRECATED: Use violation_time_limit_seconds instead. Sets a time limit, in hours, that will automatically force-close a long-lasting incident after the time limit you select. Possible values are ONE_HOUR, TWO_HOURS, FOUR_HOURS, EIGHT_HOURS, TWELVE_HOURS, TWENTY_FOUR_HOURS, THIRTY_DAYS (case insensitive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

Deprecated:

use violation_time_limit_seconds attribute instead

Sets a time limit, in seconds, that will automatically force-close a long-lasting incident after the time limit you select. The value must be between 300 seconds (5 minutes) to 2592000 seconds (30 days) (inclusive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

A list containing the warning threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

A NRQL query. See NRQL below for details.

The ID of the policy where this condition should be used.

The New Relic account ID of the account you wish to create the condition. Defaults to the account ID set in your environment variable NEW_RELIC_ACCOUNT_ID.

How long we wait for data that belongs in each aggregation window. Depending on your data, a longer delay may increase accuracy but delay notifications. Use aggregation_delay with the event_flow and cadence methods. The maximum delay is 1200 seconds (20 minutes) when using event_flow and 3600 seconds (60 minutes) when using cadence. In both cases, the minimum delay is 0 seconds and the default is 120 seconds. aggregation_delay cannot be set with nrql.evaluation_offset.

Determines when we consider an aggregation window to be complete so that we can evaluate the signal for incidents. Possible values are cadence, event_flow or event_timer. Default is event_flow. aggregation_method cannot be set with nrql.evaluation_offset.

How long we wait after each data point arrives to make sure we've processed the whole batch. Use aggregation_timer with the event_timer method. The timer value can range from 0 seconds to 1200 seconds (20 minutes); the default is 60 seconds. aggregation_timer cannot be set with nrql.evaluation_offset.

The duration of the time window used to evaluate the NRQL query, in seconds. The value must be at least 30 seconds, and no more than 900 seconds (15 minutes). Default is 60 seconds.

The baseline direction of a baseline NRQL alert condition. Valid values are: lower_only, upper_and_lower, upper_only (case insensitive).

Whether to close all open incidents when the signal expires.

A list containing the critical threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

The description of the NRQL alert condition.

Whether to enable the alert condition. Valid values are true and false. Defaults to true.

How long we wait until the signal starts evaluating. The maximum delay is 7200 seconds (120 minutes).

The amount of time (in seconds) to wait before considering the signal expired. The value must be at least 30 seconds, and no more than 172800 seconds (48 hours).

Which strategy to use when filling gaps in the signal. Possible values are none, last_value or static. If static, the fill_value field will be used for filling gaps in the signal.

This value will be used for filling gaps in the signal.

The title of the condition.

Whether to create a new incident to capture that the signal expired.

Runbook URL to display in notifications.

Gathers data in overlapping time windows to smooth the chart line, making it easier to spot trends. The slide_by value is specified in seconds and must be smaller than and a factor of the aggregation_window.

DEPRECATED Use critical, and warning instead. A list of terms for this condition. See Terms below for details.

Deprecated:

use critical and warning attributes instead

The type of the condition. Valid values are static or baseline. Defaults to static.

DEPRECATED: Use violation_time_limit_seconds instead. Sets a time limit, in hours, that will automatically force-close a long-lasting incident after the time limit you select. Possible values are ONE_HOUR, TWO_HOURS, FOUR_HOURS, EIGHT_HOURS, TWELVE_HOURS, TWENTY_FOUR_HOURS, THIRTY_DAYS (case insensitive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

Deprecated:

use violation_time_limit_seconds attribute instead

Sets a time limit, in seconds, that will automatically force-close a long-lasting incident after the time limit you select. The value must be between 300 seconds (5 minutes) to 2592000 seconds (30 days) (inclusive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

A list containing the warning threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

A NRQL query. See NRQL below for details.

The ID of the policy where this condition should be used.

The New Relic account ID of the account you wish to create the condition. Defaults to the account ID set in your environment variable NEW_RELIC_ACCOUNT_ID.

How long we wait for data that belongs in each aggregation window. Depending on your data, a longer delay may increase accuracy but delay notifications. Use aggregation_delay with the event_flow and cadence methods. The maximum delay is 1200 seconds (20 minutes) when using event_flow and 3600 seconds (60 minutes) when using cadence. In both cases, the minimum delay is 0 seconds and the default is 120 seconds. aggregation_delay cannot be set with nrql.evaluation_offset.

Determines when we consider an aggregation window to be complete so that we can evaluate the signal for incidents. Possible values are cadence, event_flow or event_timer. Default is event_flow. aggregation_method cannot be set with nrql.evaluation_offset.

How long we wait after each data point arrives to make sure we've processed the whole batch. Use aggregation_timer with the event_timer method. The timer value can range from 0 seconds to 1200 seconds (20 minutes); the default is 60 seconds. aggregation_timer cannot be set with nrql.evaluation_offset.

The duration of the time window used to evaluate the NRQL query, in seconds. The value must be at least 30 seconds, and no more than 900 seconds (15 minutes). Default is 60 seconds.

The baseline direction of a baseline NRQL alert condition. Valid values are: lower_only, upper_and_lower, upper_only (case insensitive).

Whether to close all open incidents when the signal expires.

A list containing the critical threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

The description of the NRQL alert condition.

Whether to enable the alert condition. Valid values are true and false. Defaults to true.

How long we wait until the signal starts evaluating. The maximum delay is 7200 seconds (120 minutes).

The amount of time (in seconds) to wait before considering the signal expired. The value must be at least 30 seconds, and no more than 172800 seconds (48 hours).

Which strategy to use when filling gaps in the signal. Possible values are none, last_value or static. If static, the fill_value field will be used for filling gaps in the signal.

This value will be used for filling gaps in the signal.

The title of the condition.

Whether to create a new incident to capture that the signal expired.

Runbook URL to display in notifications.

Gathers data in overlapping time windows to smooth the chart line, making it easier to spot trends. The slide_by value is specified in seconds and must be smaller than and a factor of the aggregation_window.

DEPRECATED Use critical, and warning instead. A list of terms for this condition. See Terms below for details.

Deprecated:

use critical and warning attributes instead

The type of the condition. Valid values are static or baseline. Defaults to static.

DEPRECATED: Use violation_time_limit_seconds instead. Sets a time limit, in hours, that will automatically force-close a long-lasting incident after the time limit you select. Possible values are ONE_HOUR, TWO_HOURS, FOUR_HOURS, EIGHT_HOURS, TWELVE_HOURS, TWENTY_FOUR_HOURS, THIRTY_DAYS (case insensitive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

Deprecated:

use violation_time_limit_seconds attribute instead

Sets a time limit, in seconds, that will automatically force-close a long-lasting incident after the time limit you select. The value must be between 300 seconds (5 minutes) to 2592000 seconds (30 days) (inclusive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

A list containing the warning threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

A NRQL query. See NRQL below for details.

The ID of the policy where this condition should be used.

The New Relic account ID of the account you wish to create the condition. Defaults to the account ID set in your environment variable NEW_RELIC_ACCOUNT_ID.

How long we wait for data that belongs in each aggregation window. Depending on your data, a longer delay may increase accuracy but delay notifications. Use aggregation_delay with the event_flow and cadence methods. The maximum delay is 1200 seconds (20 minutes) when using event_flow and 3600 seconds (60 minutes) when using cadence. In both cases, the minimum delay is 0 seconds and the default is 120 seconds. aggregation_delay cannot be set with nrql.evaluation_offset.

Determines when we consider an aggregation window to be complete so that we can evaluate the signal for incidents. Possible values are cadence, event_flow or event_timer. Default is event_flow. aggregation_method cannot be set with nrql.evaluation_offset.

How long we wait after each data point arrives to make sure we've processed the whole batch. Use aggregation_timer with the event_timer method. The timer value can range from 0 seconds to 1200 seconds (20 minutes); the default is 60 seconds. aggregation_timer cannot be set with nrql.evaluation_offset.

The duration of the time window used to evaluate the NRQL query, in seconds. The value must be at least 30 seconds, and no more than 900 seconds (15 minutes). Default is 60 seconds.

The baseline direction of a baseline NRQL alert condition. Valid values are: lower_only, upper_and_lower, upper_only (case insensitive).

Whether to close all open incidents when the signal expires.

A list containing the critical threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

The description of the NRQL alert condition.

Whether to enable the alert condition. Valid values are true and false. Defaults to true.

How long we wait until the signal starts evaluating. The maximum delay is 7200 seconds (120 minutes).

The amount of time (in seconds) to wait before considering the signal expired. The value must be at least 30 seconds, and no more than 172800 seconds (48 hours).

Which strategy to use when filling gaps in the signal. Possible values are none, last_value or static. If static, the fill_value field will be used for filling gaps in the signal.

This value will be used for filling gaps in the signal.

The title of the condition.

Whether to create a new incident to capture that the signal expired.

Runbook URL to display in notifications.

Gathers data in overlapping time windows to smooth the chart line, making it easier to spot trends. The slide_by value is specified in seconds and must be smaller than and a factor of the aggregation_window.

DEPRECATED Use critical, and warning instead. A list of terms for this condition. See Terms below for details.

Deprecated:

use critical and warning attributes instead

The type of the condition. Valid values are static or baseline. Defaults to static.

DEPRECATED: Use violation_time_limit_seconds instead. Sets a time limit, in hours, that will automatically force-close a long-lasting incident after the time limit you select. Possible values are ONE_HOUR, TWO_HOURS, FOUR_HOURS, EIGHT_HOURS, TWELVE_HOURS, TWENTY_FOUR_HOURS, THIRTY_DAYS (case insensitive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

Deprecated:

use violation_time_limit_seconds attribute instead

Sets a time limit, in seconds, that will automatically force-close a long-lasting incident after the time limit you select. The value must be between 300 seconds (5 minutes) to 2592000 seconds (30 days) (inclusive). *Note: One of violation_time_limit or violation_time_limit_seconds must be set, but not both.

A list containing the warning threshold values. At least one critical or warning threshold must be defined. See Terms below for details.

The unique entity identifier of the NRQL Condition in New Relic.

The provider-assigned unique ID for this managed resource.

The unique entity identifier of the NRQL Condition in New Relic.

The provider-assigned unique ID for this managed resource.

The unique entity identifier of the NRQL Condition in New Relic.

The provider-assigned unique ID for this managed resource.

The unique entity identifier of the NRQL Condition in New Relic.

The provider-assigned unique ID for this managed resource.

The unique entity identifier of the NRQL Condition in New Relic.

The provider-assigned unique ID for this managed resource.

The unique entity identifier of the NRQL Condition in New Relic.

The provider-assigned unique ID for this managed resource.