Instance Constructors

1.  new CustomElasticsearchAlert(alertName: String, checkIntervalMinutes: CheckIntervalMinutes, kibanaDashboardUri: Option[String], integrations: Seq[String], luceneQuery: String, operator: EvaluationOperator, reducerFunction: ReducerFunction, runbookUrl: Option[String], severity: CustomAlertSeverity.AlertSeverity, summary: String, teamName: String, thresholds: EnvironmentThresholds, evaluationPeriodStartMinutesAgo: TimeRangeAsMinutes, evaluationPeriodEndMinutesAgo: TimeRangeAsMinutes = TimeRangeAsMinutes.ONE_MINUTE)
   alertName

   Name that the alert will be created with

   checkIntervalMinutes

   Number of minutes between each check. See CheckIntervalMinutes for supported values

   kibanaDashboardUri

   Kibana uri to link to. This should just be the uri path and not include the domain

   integrations

   Which PagerDuty integrations to direct this alert to n

   luceneQuery

   Query to make to Elasticsearch

   operator

   Whether to evaluate the metric as greater than or less than

   reducerFunction

   Function to use to transform multiple data points returned from query into a single value, to be compared against the specified threshold. Valid values include: COUNT, LAST, MAX, MEAN, MIN, SUM. Note: Using the LAST reducer could result in not all data points being considered during alert evaluation, depending on the frequency at which the alert runs. Example: An alert with a LAST reducer, that runs every 2 minutes, based on a metric that is written on a per minute basis, will only consider ~50% of the data points, potentially missing a legitimate breach of an alert threshold.

   runbookUrl

   Runbook for when this alert fires

   severity

   The severity of this alert. E.g. Warning or Critical

   summary

   The description to populate in PagerDuty when the alert fires

   teamName

   All alerts are prefixed with the team name

   thresholds

   Trigger point for each environment

   evaluationPeriodStartMinutesAgo

   The start of the evaluation period. If you set to FIFTEEN_MINUTES, the alert check will evaluate data starting fifteen minutes ago up until evaluationPeriodEndMinutesAgo

   evaluationPeriodEndMinutesAgo

   The end of the evaluation period. If you set it to ONE MINUTE, the alert check will evaluate data starting from evaluationPeriodStartMinutesAgo until one minute ago. Less than one minute ago is not advised because these metrics may not yet be fully shipped.