alerts/tomcat/metadata.yaml

alert_policy_templates:
-
  id: tomcat-low-request-rate
  display_name: Tomcat - low request rate
  description: "The request rate is derived from the requests metrics taken as a rate
    every 5 minutes. This value should be monitored beforehand to understand what
    qualifies as a normal request rate so a threshold can be established. When request
    rate is above this threshold, then that means there is a large spike in traffic
    which logs can help diagnose if these are nefarious requests."
  version: 1
  related_integrations:
    - id: tomcat
      platform: GCE
-
  id: tomcat-high-request-rate
  display_name: Tomcat - high request rate
  description: "The request rate is derived from the requests metrics taken as a rate
    every 5 minutes. This value should be monitored beforehand to understand what
    qualifies as a normal request rate so a threshold can be established. When request
    rate is above this threshold, then that means there is a large spike in traffic
    which logs can help diagnose if these are nefarious requests."
  version: 1
  related_integrations:
    - id: tomcat
      platform: GCE
-
  id: tomcat-high-server-error-rate
  display_name: Tomcat - high server error rate
  description: "The server error rate is derived from processing access logs status
    code. The server error rate value is the number of 5xx status codes per 5 minute
    window. When the server error rate spikes suddenly, then you have a high priority
    server problem as backends are experiencing 5xx errors and clients are not being
    served successfully."
  version: 1
  related_integrations:
    - id: tomcat
      platform: GCE