Skip to content

Azure monitoring module #86

Closed
Closed
@James-Nance

Description

Description

As a developer, I can route metrics (a signal type) from an Azure App Service Plan (cobalt-azure-simple-sp) using Azure Monitoring to trigger alerts based on minimal criteria defined from an alert rule.

Acceptance Criteria

Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)

  • A module level readme that reveals minimal configuration attributes for the Azure monitoring module.
  • A main.tf file clearly dedicated to using azurerm_monitor_metric_alert as a resource.
  • An Azure Monitoring module that derives it's App Service Plan value from the Azure Simple Template. An App Service Plan can have many App Services. An App Service can not have many App Service plans.
  • A screenshot of Azure Monitoring alert rules displayed from within the Azure portal. Configuration should reflect an alert rule that takes action based on a metric of concern emitted from Azure App Service Plan (cobalt-azure-simple-sp).

Resources

Azure Monitor Overview - https://docs.microsoft.com/en-us/azure/azure-monitor/overview
Azure Monitor Alerts Overview - https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-overview
Azure Monitor Alerts ARM Template - https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-metric-create-templates
Azure Monitor Supported Metrics - https://docs.microsoft.com/en-us/azure/azure-monitor/platform/metrics-supported

Tasks

  1. Validate and discuss what required variables and resources are needed as configurable attributes for the azure monitoring metric resource. (Is the cobalt-azure-simple-sp enough? Should we setup rules for the other resources like the gateway, vnet or app insights? What about smart groups?)

  2. Decide which variables obtain their values from outside the azure monitoring module. (What variables should the Monitoring Module expose to the azure simple template? (ex. resource group name, resource group location))

  3. Validate and discuss which modules will consume the output from the app monitoring module.

  4. Choose which default/optional variables would be nice-to-haves.

  5. Implement and test deployment of the Azure Monitoring Module via the Azure Simple Template.

Metadata

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions