Azure App-Services

Learn about the other Azure service support on our Azure docs.

Sensor (Data Collection)

Tracked Configuration

App-Service Details Description
Name The name of the app-service.
Resource Group The resource-group the app-service belongs to
Location The region where the app-service is located
Subscription Id The subscription ID of the app-service
State The current state of the app-service

Metrics

App-Service Metric Description
Response-Times and Requests
Response Time The response-time for requests to your app-service
Total Requests Total number of requests within a minute
Queued Requests Number of requests that have been queued in a minute
Http Status-Codes
Http 2xx Responses Number of http-responses with an http-status between 200 and 299
Http 4xx Responses Number of http-responses with an http-status between 400 and 499
Http 5xx Responses Number of http-responses with an http-status between 500 and 599
Network traffic Metrics
Bytes sent Number of bytes sent
Bytes received Number of bytes received by the app-service
Garbage Collection Metrics
Generation 0 Number of GC-runs on Generation 0 within a minute
Generation 1 Number of GC-runs on Generation 1 within a minute
Generation 2 Number of GC-runs on Generation 2 within a minute

Configuration

Azure App Service sensor can be disabled and it can be filtered by tags and resource groups. It is possible to configure Azure App Service sensor via agent configuration in <agentinstall_dir>/etc/instana/configuration.yaml by:

com.instana.plugin.azure.appservice:
    # Valid values: true, false
    enabled: false # enabled (true) by default
    # Comma separated list of tags in key:value format
    include_tags: 
    # Comma separated list of tags in key:value format
    exclude_tags: 
    # Comma separated list of resource groups
    include_resource_groups: 
    # Comma separated list of resource groups
    exclude_resource_groups: 

Azure App Service sensor can be disabled. To disable monitoring of the Azure App Services use the folowing configuration:

com.instana.plugin.azure.appservice:
    enabled: false

Multiple tags and resource groups can be defined, separated by a comma. Tags should be provided as a key-value pair separated by :. In order to make configuration easier, it is possible to define which tags and resource groups you want to include in discovery or exclude from discovery. In case of defining tag or resource group in both lists (include and exclude), exclude list has higher priority. If there is no need for services filtering, the configuration should not be defined. It’s not mandatory to define all values in order to enable filtering.

To include services by tags into discovery use folowing configuration:

com.instana.plugin.azure.appservice:
    include_tags: # Comma separated list of tags in key:value format (e.g. env:prod,env:staging)

To exclude services by tags from discovery use folowing configuration:

com.instana.plugin.azure.appservice:
    exclude_tags: # Comma separated list of tags in key:value format (e.g. env:dev,env:test)

To include services by resource groups into discovery use folowing configuration:

com.instana.plugin.azure.appservice:
    include_resource_groups: # Comma separated list of resource groups (e.g. rg_prod,rg_staging)

To exclude services by resource groups from discovery use folowing configuration:

com.instana.plugin.azure.appservice:
    exclude_resource_groups: # Comma separated list of resource groups (e.g. rg_dev,rg_test)

Discovery filtering can be configured on the global level for all Azure services. In case of defining filters for Azure App Service, global filters will be overridden. For more details about global Azure service discovery filtering visit Azure Configuration.

Note

Metrics for App-Services are pulled every minute, which is the resolution Azure provides for monitoring of these services.