Back to Druid

Alerts

docs/operations/alerts.md

latest1.5 KB
Original Source
<!-- ~ Licensed to the Apache Software Foundation (ASF) under one ~ or more contributor license agreements. See the NOTICE file ~ distributed with this work for additional information ~ regarding copyright ownership. The ASF licenses this file ~ to you under the Apache License, Version 2.0 (the ~ "License"); you may not use this file except in compliance ~ with the License. You may obtain a copy of the License at ~ ~ http://www.apache.org/licenses/LICENSE-2.0 ~ ~ Unless required by applicable law or agreed to in writing, ~ software distributed under the License is distributed on an ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~ KIND, either express or implied. See the License for the ~ specific language governing permissions and limitations ~ under the License. -->

Druid generates alerts on getting into unexpected situations.

Alerts are emitted as JSON objects to a runtime log file or over HTTP (to a service such as Apache Kafka). Alert emission is disabled by default.

All Druid alerts share a common set of fields:

  • timestamp - the time the alert was created
  • service - the service name that emitted the alert
  • host - the host name that emitted the alert
  • severity - severity of the alert e.g. anomaly, component-failure, service-failure etc.
  • description - a description of the alert
  • data - if there was an exception then a JSON object with fields exceptionType, exceptionMessage and exceptionStackTrace