Skip to content

Latest commit

 

History

History
78 lines (63 loc) · 3.8 KB

appinsights-configuration.md

File metadata and controls

78 lines (63 loc) · 3.8 KB
Raw

Appinsights Configuration

You can configure Application Insights as a Ingress Monitor by using below configuration:

Key Description
name Name of the provider (e.g. AppInsights)
appInsightsConfig appInsightsConfig is the configuration specific to Appinsights Instance as mentioned below:

Appinsights Configuration:

Key Description
name Name of the Appinsights Instance
resourceGroup Resource group of Appinsights
location The location of the resource group.
geoLocation Location ID for the webtest to run from. For example: ["us-tx-sn1-azr", "us-il-ch1-azr"]
emailAction (Optional) Email Action is optional, This will enable monitoring alerts for ping test failure.
webhookAction (Optional) Webhook Action is also optional, You can use webhooks to route an Azure alert notification for custom actions.

Email Action:

  • send_to_service_owners: send email to all service owners, Possible values: true, false
  • custom_emails: list of email ids, For example: ["[email protected]", "[email protected]"]

Webhook Action:

  • service_uri: Webhook url, For example: http://webhook-test.io

Example Configuration:

providers:
  - name: AppInsights
    appInsightsConfig:
      name: demo-appinsights
      resourceGroup: demoRG
      location: "westeurope"
      geoLocation:
        [
          "us-tx-sn1-azr",
          "emea-nl-ams-azr",
          "us-fl-mia-edge",
          "latam-br-gru-edge",
        ]
      emailAction:
        send_to_service_owners: false
        custom_emails: ["[email protected]"]
      webhookAction:
        service_uri: http://myalert-webhook.io
enableMonitorDeletion: true

Additional Configuration

Additional Appinsights configurations can be added in the EndpointMonitor, current supported configuration attributes are:

Fields Description
StatusCode Returned status code that is counted as a success. Possible values: HTTP Status Codes
RetryEnable If its true, falied test will be retry after a short interval. Possible values: true, false
Frequency Sets how often the test should run from each test location. Possible values: 300,600,900 seconds

Example:

apiVersion: endpointmonitor.stakater.com/v1alpha1
kind: EndpointMonitor
metadata:
  name: stakater
spec:
  forceHttps: true
  url: https://stakater.com/
  appInsightsConfig:
    statusCode: 404
    retryEnable: true
    frequency: 900