Skip to content

Latest commit

 

History

History
41 lines (28 loc) · 1.73 KB

portalfx-telemetry-alerting-overview.md

File metadata and controls

41 lines (28 loc) · 1.73 KB
Raw

Overview

What are the alerts?

There are number of framework level provided alerts:

  1. Extension SDK age (Sev3 IcM incdient for an extension when its SDK is older than 60 days and Sev2 for over 90 days)
  2. Extension alive
  3. Create regression
  4. Availability
  5. Performance
  6. Client Error

The framework provides a per extension configurable alerting infrastructure, this will cover:

  1. Create
  2. Availability
  3. Performance
  4. Client Error

Once the thresholds for any of the configured alerts are met or surpassed a ICM alert containing details will be opened agaisnt the owning team.

What is configurable?

Each area will be configurable to it's own extent, allowing various levels of custom configuration.

Is National Cloud Supported?

Alerts are supported in national clouds by specifying national cloud portal domain names in "environment" property in alert customization Json. See the sub categories for further details. Its subject title is 'Is National Cloud Supported?'.

How mapping is done from extension name to IcM team and service names?

Azure Portal partner team's IcM info is collected during parnter onboarding process and is stored in spreadsheet at https://aka.ms/portalfx/partners. An IcM routing rule is added under Azure Portal (Ibiza) service in IcM to route incidents to corresponding partners.

The IcM routing rule is in format 'AIMS://AZUREPORTAL\Portal{ExtensionName}'.