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.

Azure Monitoring Overview

1,499 views

Published on

Introduction to Azure Monitor, Azure Application Insights and Azure Log Analytics (aka OMS) with some example dashboards.

Published in: Internet
  • Be the first to comment

Azure Monitoring Overview

  1. 1. What is DevOps
  2. 2. Visibility – Get the Big Picture Near Real-time Alerts & Notifications Multi-Dimensional Metrics Health & Availability Monitoring Azure Dashboards Insights – Find & Fix Problems Composite Application & Service Maps Distributed Transaction Tracing Advanced Analytics with ML Automated Actions & Remediations Optimization – Build, Measure, Learn Performance Optimization & Profiling User Behaviour & Customer Insights Impact Correlation Integration with Dev/DevOps Tools
  3. 3. Built-In monitoring support for Azure resources Out-of-box metrics and logs Alert rules to get notified & take automated actions APIs for 3rd party integration Enables advanced monitoring and analytics experiences
  4. 4. • Track the performance of your resource (such as a VM, website, or logic app) by plotting its metrics on a portal chart and pinning that chart to a dashboard. • Get notified of an issue that impacts the performance of your resource when a metric crosses a certain threshold. • Configure automated actions, such as autoscaling a resource or firing a runbook when a metric crosses a certain threshold. • Perform advanced analytics or reporting on performance or usage trends of your resource. • Archive the performance or health history of your resource for compliance or auditing purposes https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-supported-metrics
  5. 5. Leverage advanced Machine Learning (ML) capabilities to learn metrics' historical behavior to automatically calculate baselines and use them as alert thresholds The benefits of using dynamic thresholds are: • Save the hassle associated with setting a predefined rigid boundary as the monitor automatically learns the historical performance of the metric and applies ML algorithms to determine alert thresholds. • They can identify seasonal behavior and alert only on deviations from the expected seasonal behavior. Metric alerts with dynamic thresholds will not trigger if your service is regularly idle on the weekends and then spikes every Monday. Currently supported: hourly, daily, and weekly seasonality. • Continuously learns the metric performance and is adaptive to metric changes.
  6. 6. windows computers drill-down
  7. 7. Average %CPU
  8. 8. Log Analytics (OMS)
  9. 9. Log type Log analytics supporting JSON (Splunk, ELK) HP ArcSight IBM QRadar AAD Audit logs Yes Requires the creation of a FlexConnector JSON parser file. Please refer to the ArcSight documentation for more information You must create a Log Source Extension. Please refer to the QRadar documentation for more information. Activity Logs Yes FlexConnector JSON parser file available in the download center along with Azure log integration download QRadar DSM(send over Syslog) ASC Alerts Yes Requires the creation of a FlexConnector JSON parser file. Please refer to the ArcSight documentation for more information. QRadar DSM (send over Syslog) Diagnostics Logs (resource logs) Yes Needs end user to create FlexConnector JSON parser file. Please refer to ArcSight documentation on how to do that. You must create a Log Source Extension. Please refer to the QRadar documentation for more information VM logs Yes via Forwarded events and not thru JSON Yes via Forwarded events Yes via Forwarded events Azure Log Integration for OMS
  10. 10. IT Service Management Connector • The IT Service Management Connector integrates your existing IT Service Management (ITSM) products and services with OMS Log Analytics. • The solution has bidirectional integration with ITSM products/services: o it provides the OMS users an option to create incidents, alerts, or events in ITSM solution. o it imports data such as incidents, and change requests from ITSM solution into OMS Log Analytics. • Supported ITSM products: • System Center Service Manager (SCSM) • ServiceNow • Provance • Cherwell
  11. 11. You install a small instrumentation package in your application, and set up an Application Insights resource in the Microsoft Azure portal. The instrumentation monitors your app and sends telemetry data to the portal. You can instrument not only the web service application, but also any background components, and the JavaScript in the web pages themselves.
  12. 12. The main categories are: • Web server telemetry - HTTP requests. Uri, time taken to process the request, response code, client IP address, Session id. • Web pages - Page, user and session counts. Page load times. Exceptions. Ajax calls. • Performance counters - Memory, CPU, IO, Network occupancy. • Client and server context - OS, locale, device type, browser, screen resolution. • Exceptions and crashes - stack dumps, build id, CPU type. • Dependencies - calls to external services such as REST, SQL, AJAX. URI or connection string, duration, success, command. • Availability tests - duration of test and steps, responses. • Trace logs and custom telemetry - anything you code into your logs or telemetry.
  13. 13. • At run time: instrument your web app on the server. Avoids any update to the code. You need admin access to your server. o IIS on-premises or on a VM o Azure web app or VM o J2EE • At development time: add Application Insights to your code. Allows you to write custom telemetry and to instrument back-end and desktop apps. o Visual Studio 2013 update 2 or later. o Java in Eclipse or other tools o Node.js o Other platforms • Instrument your web pages for page view, AJAX and other client-side telemetry. • Availability tests - ping your website regularly from our servers.
  14. 14. • Log4Net, NLog, or System.Diagnostics.Trace • Java, Log4J, or Logback • Semantic Logging (SLAB) - integrates with Semantic Logging Application Block • Cloud-based load testing • LogStash plugin • OMS Log Analytics • Logary You can have your trace logs sent automatically to Application Insights where you can explore and search on them.
  15. 15. // Track Page View telemetry.TrackPageView("GameReviewPage"); // Track Event telemetry.TrackEvent("WinGame"); // Track Metric var sample = new MetricTelemetry(); sample.Name = "metric name"; sample.Value = 42.3; telemetry.TrackMetric(sample); // Track Exception try { ... } catch (Exception ex) { telemetry.TrackException(ex); } // Track Trace telemetry.TrackTrace(message, SeverityLevel.Warning, properties);
  16. 16. Application Map
  17. 17. Availability
  18. 18. Performance View
  19. 19. User Retention User Analysis
  20. 20. Funnel
  21. 21. https://docs.microsoft.com/en-us/azure/application-insights/app-insights-analytics-import
  22. 22. https://docs.microsoft.com/en-us/azure/application-insights/app-insights-analytics-import
  23. 23. Application Insights Custom Logs logstash + Application Insights plugin Power BI Custom Logs Operations Management Suite Agent Operations Management Suite (Log Analytics) https://docs.microsoft.com/it-it/azure/application-insights/app-insights-export-power-bi https://docs.microsoft.com/it-it/azure/log-analytics/log-analytics-powerbi
  24. 24. Resources Azure Monitor documentation: https://aka.ms/azmondocs→ Application Insights Demo https://analytics.applicationinsights.io/demo→ Application Insights Demo https://portal.loganalytics.io/demo→

×