The time frame in seconds

A list of application names for which to get the metric

A list of metrics to use

The name of the dashboard that will be created in New Relic

A list of widgets to add to the dashboard

The text shown on the widget. Use in conjunction with visualization: markdown

The NRQL query used which defines the data to plot in the widget

The APM metric parameters which defines the data to plot in the widget.
When using an APM metric for the data, visualization should be set to either metric_line_chart or application_breakdown.

Name of the metric

List of metric values to plot. The available values will depend on the metric you choose.
Check the Data Explorer in New Relic to find out which values are available for which metrics.

The title of the widget created in New Relic

Visualization type to use for the widget.
Available options are:
- application_breakdown
- attribute_sheet
- background_breakdown
- billboard
- billboard_comparison
- comparison_line_chart
- event_table
- facet_bar_chart
- facet_pie_chart
- facet_table
- faceted_area_chart
- faceted_line_chart
- funnel
- gauge
- heatmap
- histogram
- json
- line_chart
- markdown
- list
- metric_line_chart (used for apm metrics)

Notes to add to the widget

The data to plot on the widget

Defines the layout of the widget within the dashboard

The name of the alert policy that will be created in New Relic

The incident preference defines when incident should be created.
Can be one of:
- per_policy
- per_condition
- per_condition_and_target

A list of APM alert conditions to attach to the policy

A list of NRQL alert conditions to attach to the policy

A list of Infrastructure alert conditions to attach to the policy

The name of the alert condition that will be created in New Relic

The type of the metric to monitor. Should be one of:
- apm_app_metric
- apm_kt_metric
- apm_jvm_metric
- browser_metric
- mobile_metric
Please refer to the Alerts conditions section in the New Relic documentation for more details

default: true

A list of application names from APM to monitor

The APM metric to monitor. Different metrics can be applied depending on the condition type.
An example of a valid (type, metric) combination is (apm_app_metric, apdex).
Please refer to the Alerts conditions section in the New Relic documentation for more details

Once the alertThreshold is breached, a critical incident will be generated

Once the warningThreshold is breached, a warning will be generated

Used for tracking a user defined custom metric
For more information, please refer to the New Relic documentation

(Members of AbstractNotificationChannel are embedded into this type.)

The name of the notification channel created in New Relic

A comma-separated value of emails

default: false

Include JSON attachment with the notification

A label selector defining the alert policies covered by the notification channel

How long to wait, in seconds, after the last data point is received by our platform before considering the signal as lost. For more information, please refer to the official New Relic documentation

When true, this closes all currently open violations when no signal is heard within the expiration_duration time. For more information, please refer to the official New Relic documentation

When true, this opens a loss of signal violation when no signal within the expiration_duration time. For more information, please refer to the official New Relic documentation

The name of the infra condition that will be created in New Relic

Available options are:
- above
- below
- equal

Once the alertThreshold is breached, a critical incident will be generated

Once the warningThreshold is breached, a warning will be generated

default: true

Leave this parameter empty when creating conditions based on data from an integration provider For more information, please refer to the event_type field in the official New Relic documentation

When setting up alerts on integrations, specify the corresponding integration provider.
Examples can include SqsQueue, Kubernetes, RdsDbInstance etc.
For more information, please refer to the integration_provider field in the official New Relic documentation

The attribute name from the Event sample or Integration provider which identifies the metric to be tracked. Examples for Sqs include provider.approximateAgeOfOldestMessage.Average and provider.numberOfEmptyReceives.Average. For more information, please refer to the select_value field in the official New Relic documentation

An expression used for filtering data from the IntegrationProvider

Defines when the threshold should be considered as breached.
Available options are:
- all - all data points are in violation within the given period
- any - at least one data point is in violation within the given period

For how long the violation should be active before an incident is triggered

(Members of Status are embedded into this type.)

The name of the nrql policy that will be created in New Relic

default: true

The NRQL query associated with the condition

Defines the SINCE clause in the NRQL query

Available options are:
- single_value
- sum
For more information, please refer to the official New Relic documentation

Once the alertThreshold is breached, a critical incident will be generated

Once the warningThreshold is breached, a warning will be generated

Used to specify signal properties for missing data

Used to define actions on signal expiration

(Members of AbstractNotificationChannel are embedded into this type.)

The name of the notification channel created in New Relic

The Opsgenie API Key. If left empty, the default API key specified when deploying the operator will be used

A list of teams

A list of tags

A comma-separated value of emails

A label selector defining the alert policies covered by the notification channel

Please refer to the official New Relic documentation

The offset is how long we wait for late data before evaluating each aggregation window For additional information, please refer to the official New Relic documentation

For sporadic data, you can avoid false alerts by filling the gaps (empty windows) with synthetic data. The default is None. For additional information, please refer to the official New Relic documentation

This is the value used by the fill_option custom value. The default is 0. For additional information, please refer to the official New Relic documentation

(Members of AbstractNotificationChannel are embedded into this type.)

The name of the notification channel created in New Relic

The Slack webhook URL. If left empty, the default URL specified when deploying the operator will be used

Name of the Slack channel. Should start with #

A label selector defining the alert policies covered by the notification channel

Defines when the threshold should be considered as breached.
Available options are:
* all - all data points are in violation within the given period
* any - at least one data point is in violation within the given period
For more information, please refer to the official New Relic documentation

Available options are:
- above
- below
- equal

For how long the violation should be active before an incident is triggered
For more information, please refer to the official New Relic documentation

The name of the user defined custom metric

Available options are:
- average
- min
- max
- total
- sample_size
For more information, please refer to the official New Relic documentation

The value will be set to Ready once the policy has been created in New Relic

When a policy fails to be created, the value will be set to the error message received from New Relic

The resource id in New Relic