Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Monitoring and Alerting with InfluxDB 2.0 | Deniz Kusefoglu & Nate Isley | InfluxDB


Published on

In this talk we’ll go over the new UI and API in InfluxDB 2.0 to create complex monitoring, alerting and notification rules. We’ll start with the easy on-ramp via the user interface and then dig into how the setup and management of monitoring and alerting can be driven through code and the API.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Monitoring and Alerting with InfluxDB 2.0 | Deniz Kusefoglu & Nate Isley | InfluxDB

  1. 1. Deniz Kusefoglu and Nate Isley Monitoring and Alerting with InfluxDB 2.0
  2. 2. Agenda • Vision • Building blocks of Monitoring & Alerting • Classifying your Alerts with Tags • Leveraging Status and Notification Messages • Engineering Deep Dive
  3. 3. Vision for Monitoring & Alerting in 2.0 • Easy to use interface • A point-and-click user experience for all! • Deliver value on top of InfluxDB 2 primitives • Power users unite!
  4. 4. Monitoring & Alerting
  5. 5. Building Blocks ( Checks, Endpoints, Rules )
  6. 6. Terminology: Checks Query A Flux script that returns time series data Check Analyzes the results of a Query to determine the current Status against the check criteria. Tags Flexible user defined Key/Value pairs put on Status Status The Level and Tags of a Check written to the Monitoring Bucket
  7. 7. Terminology: Checks Monitoring Bucket System bucket where a Check stores the current Status There are two different Check Types Threshold Periodically check calculated values against thresholds to determine Status Deadman Periodically check if values are being reported to determine Status
  8. 8. Terminology: Notification Endpoints Configuration describing how to call a 3rd party service Three different Endpoints are supported in Cloud 2.0 Today Free Tier Slack Paid Tier HTTP Endpoint PagerDuty
  9. 9. Notification Rule Notification Rule Analyzes Monitoring system buckets When rule conditions are met, sends a Notification Message to the Notification Endpoint and stores a receipt in the Monitoring Bucket Records the Notification Endpoint name, Notification Message, Sent Status, and Tags used in the Check
  10. 10. M&A Building Blocks ( Checks, Endpoints, Rules )
  11. 11. Pulling it all together: A Simple Example Monitor a system’s CPU Walk Through: Threshold Check to Notification • Notify on high CPU Walk Through: Deadman Check to Notification • Notify when the system stops reporting
  12. 12. Demo
  13. 13. Monitoring & Alerting
  14. 14. Using Custom Tags to Classify Checks • Separation of team concerns • Designate responsibility for the monitored resources to a particular line-of-business, department, or scrum team • Separation of location concerns • Location contexts such as LA datacenter or Raleigh datacenter • Separation of criticality • Production vs. Staging vs. Development
  15. 15. Leveraging Status and Notification Messages Flux string interpolation is available within both Status and Notification messages. Values you can use: • Custom Tags applied to the Checks • Values from the Query • The _check_name • The _level • The _source_measurement • The _type
  16. 16. Monitoring & Alerting