Slow Query Incidents

Slow Query incidents are triggered when any data query takes too long to complete. By default, a Slow Query incident will trigger a warning if any data query takes at least 30 seconds to execute.

You can configure thresholds using the RMT Server web interface or by updating the configuration file config.json.

To set the thresholds for slow query incidents, under the Admin menu, select Configuration, and go the Incidents tab.

Key Required? Description
Severity Required

See Incident Severity Level.

Duration Required The minimum duration for a query to be considered slow. Values are in seconds.

An example config.json snippet defining a Slow Query incident:

{  
 "monitoring":  {  
    "incidents":  {  
      "triggers":  [  
        {  
          "counter":  "DataQueryDuration",  
          "severity":  "critical",  
          "threshold":  45000  
        }  
      ]  
    }  
  }  
}

This Slow Query incident will trigger if a data query takes at least 45 seconds to execute.

Incidents can be configured per environment. As an example, for an environment whose identifier was “staging-environment” to trigger a warning when a data query takes longer than 30 seconds to execute, the configuration would look like:

{  
  "environments":  {  
    "staging-environment":  {  
     "monitoring":  {  
       "incidents":  {  
          "triggers":  [  
            {  
              "counter":  "DataQueryDuration",  
              "severity":  "warning",  
              "threshold":  30000  
            }  
          ]  
        }  
      }  
    }  
  }  
}
Key Data Type Required? Description
counter String Required Slow Query incidents use the DataQueryDuration identifier.
severity String Optional See Incident Severity Level. Default value: Warning
threshold Number Required The minimum duration for a query to be considered slow. Values are in milliseconds.

Who can do this

Resource Monitoring ToolAdministrator or a Resource Monitoring Tool user with Server/Environment Management role.

Thanks for your feedback!Your feedback has been successfully submitted. Thank you!