Criar e configurar recursos do Application Insights

Sem requisitos adicionais.

Para acessar os comandos da CLI do Azure do Application Insights, primeiro você precisa executar:

az extension add -n application-insights

Se não executares o az extension add comando, vês uma mensagem de erro que diz: az : ERROR: az monitor: 'app-insights' is not in the 'az monitor' command group. See 'az monitor --help'.

Para fazer uma chamada de API REST para o Azure, primeiro você precisa obter um token de acesso.

Para obter mais informações, consulte Gerenciar recursos do Azure usando a API REST.

Você pode implantar modelos Bicep por meio da CLI do Azure, do Azure PowerShell e no portal do Azure. Verifique os respetivos separadores para requisitos adicionais.

Você pode implantar modelos ARM por meio da CLI do Azure, do Azure PowerShell e no portal do Azure. Verifique os respetivos separadores para requisitos adicionais.

1. Inicie sessão no portal Azure.
2. Selecione Criar um recurso.
3. Abra a categoria Monitoramento & Diagnóstico e selecione Application Insights.
4. Insira todas as informações relevantes e, em seguida, Revise + crie seu recurso do Application Insights.

Depois de criar seu recurso, você pode encontrar as informações correspondentes do espaço de trabalho no painel Visão geral do Application Insights.

Selecione o texto do link azul para ir para o espaço de trabalho associado do Log Analytics, onde você pode aproveitar o novo ambiente de consulta do espaço de trabalho unificado.

O exemplo seguinte da CLI do Azure utiliza o comando az monitor app-insights component create.

# Set variables
resourceGroupName="<ResourceGroupName>"
resourceName="<ResourceName>"
azureRegion="<AzureRegion>"
workspaceName="<WorkspaceName>"

# Get the subscription ID from the current Azure CLI context
subscriptionId=$(az account show --query id --output tsv)

# Build the full resource ID for the Log Analytics workspace
workspaceResourceId="/subscriptions/$subscriptionId/resourceGroups/$resourceGroupName/providers/Microsoft.OperationalInsights/workspaces/$workspaceName"

# Create a workspace-based Application Insights resource
az monitor app-insights component create \
  --app "$resourceName" \
  --location "$azureRegion" \
  --resource-group "$resourceGroupName" \
  --kind web \
  --application-type web \
  --workspace "$workspaceResourceId"

O exemplo Azure PowerShell seguinte utiliza o cmdlet New-AzApplicationInsights.

# Set variables
$resourceGroupName = "<ResourceGroupName>"
$resourceName = "<ResourceName>"
$azureRegion = "<AzureRegion>"
$workspaceName = "<WorkspaceName>"

# Get the subscription ID from the current Azure PowerShell context
$subscriptionId = (Get-AzContext).Subscription.Id

# Build the full resource ID for the Log Analytics workspace
$workspaceResourceId = "/subscriptions/$subscriptionId/resourceGroups/$resourceGroupName/providers/Microsoft.OperationalInsights/workspaces/$workspaceName"

# Define the parameters for the Application Insights resource
$newAzApplicationInsightsParams = @{
    ResourceGroupName   = $resourceGroupName
    Name                = $resourceName
    Location            = $azureRegion
    Kind                = "web"
    ApplicationType     = "web"
    WorkspaceResourceId = $workspaceResourceId
}

# Create a workspace-based Application Insights resource
New-AzApplicationInsights @newAzApplicationInsightsParams

O exemplo seguinte de REST utiliza a operação Components REST API.

PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Insights/components/{resourceName}?api-version={apiVersion}
Authorization: Bearer {accessToken}
Content-Type: application/json

{
  "kind": "web",
  "location": "<AzureRegion>",
  "properties": {
    "Application_Type": "web",
    "WorkspaceResourceId": "/subscriptions/<SubscriptionId>/resourceGroups/<ResourceGroupName>/providers/Microsoft.OperationalInsights/workspaces/<WorkspaceName>"
  }
}

O exemplo Bicep seguinte utiliza o tipo de recurso Microsoft.Insights/components.

param subscriptionId string = '<SubscriptionId>'
param resourceGroupName string = '<ResourceGroupName>'
param resourceName string = '<ResourceName>'
param azureRegion string = '<AzureRegion>'
param workspaceName string = '<WorkspaceName>'

var workspaceResourceId = '/subscriptions/${subscriptionId}/resourceGroups/${resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/${workspaceName}'

resource applicationInsightsComponent 'Microsoft.Insights/components@<ApiVersion>' = {
  name: resourceName
  location: azureRegion
  kind: 'web'
  properties: {
    Application_Type: 'web'
    WorkspaceResourceId: workspaceResourceId
  }
}

O seguinte exemplo de ARM (JSON) utiliza o Microsoft. Insights/components tipo de recurso.

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "subscriptionId": {
      "type": "string",
      "defaultValue": "<SubscriptionId>"
    },
    "resourceGroupName": {
      "type": "string",
      "defaultValue": "<ResourceGroupName>"
    },
    "resourceName": {
      "type": "string",
      "defaultValue": "<ResourceName>"
    },
    "azureRegion": {
      "type": "string",
      "defaultValue": "<AzureRegion>"
    },
    "workspaceName": {
      "type": "string",
      "defaultValue": "<WorkspaceName>"
    }
  },
  "variables": {
    "workspaceResourceId": "[format('/subscriptions/{0}/resourceGroups/{1}/providers/Microsoft.OperationalInsights/workspaces/{2}', parameters('subscriptionId'), parameters('resourceGroupName'), parameters('workspaceName'))]"
  },
  "resources": [
    {
      "type": "Microsoft.Insights/components",
      "apiVersion": "<ApiVersion>",
      "name": "[parameters('resourceName')]",
      "location": "[parameters('azureRegion')]",
      "kind": "web",
      "properties": {
        "Application_Type": "web",
        "WorkspaceResourceId": "[variables('workspaceResourceId')]"
      }
    }
  ]
}

Para obter o string de ligação do recurso do Application Insights:

1. Abra o recurso do Application Insights no portal do Azure.
2. No painel Visão geral na seção Essenciais , procure Cadeia de conexão.
3. Ao passar o rato sobre a string de conexão, aparece um ícone que permite copiá-la para a área de transferência.

O exemplo seguinte da CLI do Azure utiliza o comando az monitor app-insights component show.

# Set variables
resourceGroupName="<ResourceGroupName>"
resourceName="<ResourceName>"

# Retrieve the Application Insights component
az monitor app-insights component show \
  --resource-group "$resourceGroupName" \
  --app "$resourceName"

Procure o connectionString campo na resposta JSON.

O exemplo Azure PowerShell seguinte utiliza o cmdlet Get-AzApplicationInsights.

# Set variables
$resourceGroupName = "<ResourceGroupName>"
$resourceName = "<ResourceName>"

# Define parameters for Get-AzApplicationInsights
$getAzApplicationInsightsParams = @{
    ResourceGroupName = $resourceGroupName
    Name              = $resourceName
}

# Retrieve the Application Insights component
Get-AzApplicationInsights @getAzApplicationInsightsParams

Procure a propriedade ConnectionString na saída.

O exemplo seguinte de REST utiliza a operação Components REST API.

GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Insights/components/{resourceName}?api-version={apiVersion}
Authorization: Bearer {accessToken}

Procure o properties.connectionString campo na resposta JSON.

Não aplicável a modelos Bicep.

Não aplicável a modelos ARM.

No recurso do Application Insights, selecione Propriedades>Alterar espaço de trabalho>Log Analytics Workspaces.

O exemplo seguinte da CLI do Azure utiliza o comando az monitor app-insights component update.

# Set variables
resourceGroupName="<ResourceGroupName>"
resourceName="<ResourceName>"
workspaceName="<WorkspaceName>"

# Get the subscription ID from the current Azure CLI context
subscriptionId=$(az account show --query id --output tsv)

# Build the full resource ID for the Log Analytics workspace
workspaceResourceId="/subscriptions/$subscriptionId/resourceGroups/$resourceGroupName/providers/Microsoft.OperationalInsights/workspaces/$workspaceName"

# Update a workspace-based Application Insights resource
az monitor app-insights component update \
  --resource-group "$resourceGroupName" \
  --app "$resourceName" \
  --workspace "$workspaceResourceId"

O exemplo Azure PowerShell seguinte utiliza o cmdlet Update-AzApplicationInsights.

# Set variables
$resourceGroupName = "<ResourceGroupName>"
$resourceName = "<ResourceName>"
$workspaceName = "<WorkspaceName>"

# Get the subscription ID from the current Azure PowerShell context
$subscriptionId = (Get-AzContext).Subscription.Id

# Build the full resource ID for the Log Analytics workspace
$workspaceResourceId = "/subscriptions/$subscriptionId/resourceGroups/$resourceGroupName/providers/Microsoft.OperationalInsights/workspaces/$workspaceName"

# Define the parameters for the Application Insights resource
$updateAzApplicationInsightsParams = @{
    ResourceGroupName   = $resourceGroupName
    Name                = $resourceName
    WorkspaceResourceId = $workspaceResourceId
}

# Update a workspace-based Application Insights resource
Update-AzApplicationInsights @updateAzApplicationInsightsParams

O exemplo seguinte de REST utiliza a operação Components REST API.

PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Insights/components/{resourceName}?api-version={apiVersion}
Authorization: Bearer {accessToken}
Content-Type: application/json

{
  "location": "<AzureRegion>",
  "kind": "web",
  "properties": {
    "Application_Type": "web",
    "WorkspaceResourceId": "/subscriptions/<SubscriptionId>/resourceGroups/<ResourceGroupName>/providers/Microsoft.OperationalInsights/workspaces/<WorkspaceName>"
  }
}

O exemplo de Bicep seguinte utiliza o tipo de recurso Microsoft.Insights components.

param subscriptionId string = '<SubscriptionId>'
param resourceGroupName string = '<ResourceGroupName>'
param resourceName string = '<ResourceName>'
param azureRegion string = '<AzureRegion>'
param workspaceName string = '<WorkspaceName>'

var workspaceResourceId = '/subscriptions/${subscriptionId}/resourceGroups/${resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/${workspaceName}'

resource applicationInsightsComponent 'Microsoft.Insights/components@<ApiVersion>' = {
  name: resourceName
  location: azureRegion
  kind: 'web'
  properties: {
    Application_Type: 'web'
    WorkspaceResourceId: workspaceResourceId
  }
}

O exemplo seguinte de ARM (JSON) utiliza o tipo de recurso Microsoft.Insights components.

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "subscriptionId": {
      "type": "string",
      "defaultValue": "<SubscriptionId>"
    },
    "resourceGroupName": {
      "type": "string",
      "defaultValue": "<ResourceGroupName>"
    },
    "resourceName": {
      "type": "string",
      "defaultValue": "<ResourceName>"
    },
    "azureRegion": {
      "type": "string",
      "defaultValue": "<AzureRegion>"
    },
    "workspaceName": {
      "type": "string",
      "defaultValue": "<WorkspaceName>"
    }
  },
  "variables": {
    "workspaceResourceId": "[format('/subscriptions/{0}/resourceGroups/{1}/providers/Microsoft.OperationalInsights/workspaces/{2}', parameters('subscriptionId'), parameters('resourceGroupName'), parameters('workspaceName'))]"
  },
  "resources": [
    {
      "type": "Microsoft.Insights/components",
      "apiVersion": "<ApiVersion>",
      "name": "[parameters('resourceName')]",
      "location": "[parameters('azureRegion')]",
      "kind": "web",
      "properties": {
        "Application_Type": "web",
        "WorkspaceResourceId": "[variables('workspaceResourceId')]"
      }
    }
  ]
}

No recurso do Application Insights, selecione Configurações de diagnóstico>Adicionar configuração de diagnóstico.

Você pode selecionar todas as tabelas ou um subconjunto de tabelas para arquivar em uma conta de armazenamento. Você também pode transmitir para um hub de eventos.

O exemplo seguinte da CLI do Azure utiliza o comando az monitor diagnostic-settings create. Cria uma configuração de diagnóstico que envia registos e métricas de um recurso Application Insights para uma conta de armazenamento.

# Set variables
resourceGroupName="<ResourceGroupName>"
resourceName="<ResourceName>"
storageAccountName="<StorageAccountName>"
diagnosticSettingName="<DiagnosticSettingName>"

# Get the subscription ID from the current Azure CLI context
subscriptionId=$(az account show --query id --output tsv)

# Build the full resource ID for the Application Insights component
resourceId="/subscriptions/$subscriptionId/resourceGroups/$resourceGroupName/providers/Microsoft.Insights/components/$resourceName"

# Build the full resource ID for the storage account
storageAccountId="/subscriptions/$subscriptionId/resourceGroups/$resourceGroupName/providers/Microsoft.Storage/storageAccounts/$storageAccountName"

# Create the diagnostic setting
az monitor diagnostic-settings create \
  --name "$diagnosticSettingName" \
  --resource "$resourceId" \
  --storage-account "$storageAccountId" \
  --logs '[{"category":"AppRequests","enabled":true}]' \
  --metrics '[{"category":"AllMetrics","enabled":true}]'

O exemplo Azure PowerShell seguinte utiliza o cmdlet New-AzDiagnosticSetting. Cria uma configuração de diagnóstico que envia registos e métricas de um recurso Application Insights para uma conta de armazenamento.

# Set variables
$resourceGroupName = "<ResourceGroupName>"
$resourceName = "<ResourceName>"
$storageAccountName = "<StorageAccountName>"
$diagnosticSettingName = "<DiagnosticSettingName>"

# Get the subscription ID from the current Azure PowerShell context
$subscriptionId = (Get-AzContext).Subscription.Id

# Build the full resource ID for the Application Insights component
$resourceId = "/subscriptions/$subscriptionId/resourceGroups/$resourceGroupName/providers/Microsoft.Insights/components/$resourceName"

# Build the full resource ID for the storage account
$storageAccountId = "/subscriptions/$subscriptionId/resourceGroups/$resourceGroupName/providers/Microsoft.Storage/storageAccounts/$storageAccountName"

# Create log and metric settings objects
$log = New-AzDiagnosticSettingLogSettingsObject `
  -Category 'AppRequests' `
  -Enabled $true

$metric = New-AzDiagnosticSettingMetricSettingsObject `
  -Category 'AllMetrics' `
  -Enabled $true

# Define parameters for New-AzDiagnosticSetting
$newAzDiagnosticSettingParams = @{
    Name             = $diagnosticSettingName
    ResourceId       = $resourceId
    StorageAccountId = $storageAccountId
    Log              = @($log)
    Metric           = @($metric)
}

# Create the diagnostic setting
New-AzDiagnosticSetting @newAzDiagnosticSettingParams

O exemplo seguinte de REST utiliza a operação REST API de definições de diagnóstico . Cria uma configuração de diagnóstico que envia registos e métricas de um recurso Application Insights para uma conta de armazenamento.

PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Insights/components/{resourceName}/providers/Microsoft.Insights/diagnosticSettings/{diagnosticSettingName}?api-version={apiVersion}
Authorization: Bearer {accessToken}
Content-Type: application/json

{
  "properties": {
    "storageAccountId": "/subscriptions/<SubscriptionId>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Storage/storageAccounts/<StorageAccountName>",
    "logs": [
      {
        "category": "AppRequests",
        "enabled": true
      }
    ],
    "metrics": [
      {
        "category": "AllMetrics",
        "enabled": true
      }
    ]
  }
}

O exemplo Bicep seguinte utiliza o tipo de recurso Microsoft.Insights diagnosticSettings. Cria uma configuração de diagnóstico que envia registos e métricas de um recurso Application Insights para uma conta de armazenamento.

param subscriptionId string = '<SubscriptionId>'
param resourceGroupName string = '<ResourceGroupName>'
param resourceName string = '<ResourceName>'
param storageAccountName string = '<StorageAccountName>'
param diagnosticSettingName string = '<DiagnosticSettingName>'

resource applicationInsightsComponent 'Microsoft.Insights/components@<ApiVersion>' existing = {
  name: resourceName
}

var storageAccountId = '/subscriptions/${subscriptionId}/resourceGroups/${resourceGroupName}/providers/Microsoft.Storage/storageAccounts/${storageAccountName}'

resource diagnosticSetting 'Microsoft.Insights/diagnosticSettings@<ApiVersion>' = {
  name: diagnosticSettingName
  scope: applicationInsightsComponent
  properties: {
    storageAccountId: storageAccountId
    logs: [
      {
        category: 'AppRequests'
        enabled: true
      }
    ]
    metrics: [
      {
        category: 'AllMetrics'
        enabled: true
      }
    ]
  }
}

O seguinte exemplo de modelo ARM utiliza o Microsoft. Insights diagnosticSettings tipo de recurso. Cria uma configuração de diagnóstico que envia registos e métricas de um recurso Application Insights para uma conta de armazenamento.

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "subscriptionId": {
      "type": "string",
      "defaultValue": "<SubscriptionId>"
    },
    "resourceGroupName": {
      "type": "string",
      "defaultValue": "<ResourceGroupName>"
    },
    "resourceName": {
      "type": "string",
      "defaultValue": "<ResourceName>"
    },
    "storageAccountName": {
      "type": "string",
      "defaultValue": "<StorageAccountName>"
    },
    "diagnosticSettingName": {
      "type": "string",
      "defaultValue": "<DiagnosticSettingName>"
    }
  },
  "variables": {
    "storageAccountId": "[format('/subscriptions/{0}/resourceGroups/{1}/providers/Microsoft.Storage/storageAccounts/{2}', parameters('subscriptionId'), parameters('resourceGroupName'), parameters('storageAccountName'))]"
  },
  "resources": [
    {
      "type": "Microsoft.Insights/components/providers/diagnosticSettings",
      "apiVersion": "<ApiVersion>",
      "name": "[format('{0}/Microsoft.Insights/{1}', parameters('resourceName'), parameters('diagnosticSettingName'))]",
      "properties": {
        "storageAccountId": "[variables('storageAccountId')]",
        "logs": [
          {
            "category": "AppRequests",
            "enabled": true
          }
        ],
        "metrics": [
          {
            "category": "AllMetrics",
            "enabled": true
          }
        ]
      }
    }
  ]
}

A retenção de dados para recursos do Application Insights pode ser definida no espaço de trabalho associado do Log Analytics.

Para obter mais informações, consulte Configurar o período de retenção interativo padrão de tabelas do Google Analytics.

A retenção de dados para recursos do Application Insights pode ser definida no espaço de trabalho associado do Log Analytics.

Para obter mais informações, consulte Configurar o período de retenção interativo padrão de tabelas do Google Analytics.

A retenção de dados para recursos do Application Insights pode ser definida no espaço de trabalho associado do Log Analytics.

Para obter mais informações, consulte Configurar o período de retenção interativo padrão de tabelas do Google Analytics.

A retenção de dados para recursos do Application Insights pode ser definida no espaço de trabalho associado do Log Analytics.

Para obter mais informações, consulte Configurar o período de retenção interativo padrão de tabelas do Google Analytics.

O exemplo seguinte do Bicep utiliza o tipo de recurso Microsoft.OperationalInsights workspaces. Define o período de retenção de dados para o espaço de trabalho Log Analytics associado.

param workspaceName string = '<WorkspaceName>'
param azureRegion string = '<AzureRegion>'
param retentionInDays int = <RetentionInDays>

resource logAnalyticsWorkspace 'Microsoft.OperationalInsights/workspaces@<ApiVersion>' = {
  name: workspaceName
  location: azureRegion
  properties: {
    retentionInDays: retentionInDays
  }
}

O exemplo seguinte de ARM (JSON) utiliza o tipo de recurso Microsoft.OperationalInsights workspaces. Define o período de retenção de dados para o espaço de trabalho Log Analytics associado.

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "workspaceName": {
      "type": "string",
      "defaultValue": "<WorkspaceName>"
    },
    "azureRegion": {
      "type": "string",
      "defaultValue": "<AzureRegion>"
    },
    "retentionInDays": {
      "type": "int",
      "defaultValue": <RetentionInDays>
    }
  },
  "resources": [
    {
      "type": "Microsoft.OperationalInsights/workspaces",
      "apiVersion": "<ApiVersion>",
      "name": "[parameters('workspaceName')]",
      "location": "[parameters('azureRegion')]",
      "properties": {
        "retentionInDays": "[parameters('retentionInDays')]"
      }
    }
  ]
}

Para saber como definir o limite diário no portal do Azure, consulte Definir limite diário no espaço de trabalho do Log Analytics.

Log Analytics:

O exemplo seguinte do CLI do Azure utiliza o comando az monitor log-analytics workspace update.

# Set variables
resourceGroupName="<ResourceGroupName>"
workspaceName="<WorkspaceName>"
dailyCapInGb="<DailyCapInGb>"

# Update the daily cap for the Log Analytics workspace
az monitor log-analytics workspace update \
  --resource-group "$resourceGroupName" \
  --workspace-name "$workspaceName" \
  --set workspaceCapping.dailyQuotaGb=$dailyCapInGb

Os seguintes exemplos Azure PowerShell utilizam os cmdlets Set-AzApplicationInsightsDailyCap e Set-AzOperationalInsightsWorkspace.

Informações da Aplicação:

Os seguintes exemplos Azure PowerShell utilizam o cmdlet Set-AzApplicationInsightsDailyCap.

# Set variables
$resourceGroupName = "<ResourceGroupName>"
$resourceName = "<ResourceName>"
$dailyCapInGb = "<DailyCapInGb>"

# Define the parameters for the daily cap
$setAzApplicationInsightsDailyCapParams = @{
    ResourceGroupName = $resourceGroupName
    Name              = $resourceName
    DailyCapGB        = $dailyCapInGb
}

# Set the daily cap for the Application Insights resource
Set-AzApplicationInsightsDailyCap @setAzApplicationInsightsDailyCapParams

Log Analytics:

Os seguintes exemplos Azure PowerShell utilizam o cmdlet Set-AzOperationalInsightsWorkspace.

# Set variables
$resourceGroupName = "<ResourceGroupName>"
$workspaceName = "<WorkspaceName>"
$dailyCapInGb = "<DailyCapInGb>"

# Define the parameters for the daily cap
$setAzOperationalInsightsWorkspaceParams = @{
    ResourceGroupName = $resourceGroupName
    Name              = $workspaceName
    DailyQuotaGb      = $dailyCapInGb
}

# Set the daily cap for the Log Analytics workspace
Set-AzOperationalInsightsWorkspace @setAzOperationalInsightsWorkspaceParams

Log Analytics:

O exemplo seguinte de REST utiliza a operação da API REST do Workspaces .

PATCH https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}?api-version={apiVersion}
Authorization: Bearer {accessToken}
Content-Type: application/json

{
  "properties": {
    "workspaceCapping": {
      "dailyQuotaGb": <DailyCapInGb>
    }
  }
}

Log Analytics:

O exemplo seguinte do Bicep utiliza o tipo de recurso Microsoft.OperationalInsights workspaces.

param workspaceName string = '<WorkspaceName>'
param azureRegion string = '<AzureRegion>'
param dailyCapInGb int

resource logAnalyticsWorkspace 'Microsoft.OperationalInsights/workspaces@<ApiVersion>' = {
  name: workspaceName
  location: azureRegion
  properties: {
    workspaceCapping: {
      dailyQuotaGb: dailyCapInGb
    }
  }
}

Log Analytics:

O exemplo seguinte de ARM (JSON) utiliza o tipo de recurso Microsoft.OperationalInsights workspaces.

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "workspaceName": {
      "type": "string",
      "defaultValue": "<WorkspaceName>"
    },
    "azureRegion": {
      "type": "string",
      "defaultValue": "<AzureRegion>"
    },
    "dailyCapInGb": {
      "type": "int"
    }
  },
  "resources": [
    {
      "type": "Microsoft.OperationalInsights/workspaces",
      "apiVersion": "<ApiVersion>",
      "name": "[parameters('workspaceName')]",
      "location": "[parameters('azureRegion')]",
      "properties": {
        "workspaceCapping": {
          "dailyQuotaGb": "[parameters('dailyCapInGb')]"
        }
      }
    }
  ]
}

Para saber como definir os preços no portal do Azure, consulte Application Insights Billing.

Os exemplos seguintes da CLI do Azure utilizam o comando az monitor log-analytics workspace update.

Pagamento conforme utilização:

# Set variables
resourceGroupName="<ResourceGroupName>"
workspaceName="<WorkspaceName>"

# Set the pricing plan to pay-as-you-go
az monitor log-analytics workspace update \
  --resource-group "$resourceGroupName" \
  --workspace-name "$workspaceName" \
  --set PerGB2018

Nível de compromisso:

# Set variables
resourceGroupName="<ResourceGroupName>"
workspaceName="<WorkspaceName>"
capacityReservationInGb="<CapacityReservationInGb>"

# Set the pricing plan to commitment tier
az monitor log-analytics workspace update \
  --resource-group "$resourceGroupName" \
  --workspace-name "$workspaceName" \
  --set CapacityReservation \
  --level "$capacityReservationInGb"

Os seguintes exemplos Azure PowerShell utilizam o cmdlet Set-AzOperationalInsightsWorkspace.

Pagamento conforme utilização:

# Set variables
$resourceGroupName = "<ResourceGroupName>"
$workspaceName = "<WorkspaceName>"

# Define the parameters for the pricing plan
$setAzOperationalInsightsWorkspaceParams = @{
    ResourceGroupName = $resourceGroupName
    Name              = $workspaceName
    Sku               = "PerGB2018"
}

# Set the pricing plan to pay-as-you-go
Set-AzOperationalInsightsWorkspace @setAzOperationalInsightsWorkspaceParams

Nível de compromisso:

# Set variables
$resourceGroupName = "<ResourceGroupName>"
$workspaceName = "<WorkspaceName>"
$capacityReservationInGb = "<CapacityReservationInGb>"

# Define the parameters for the pricing plan
$setAzOperationalInsightsWorkspaceParams = @{
    ResourceGroupName = $resourceGroupName
    Name              = $workspaceName
    Sku               = "CapacityReservation"
    SkuCapacity       = $capacityReservationInGb
}

# Set the pricing plan to commitment tier
Set-AzOperationalInsightsWorkspace @setAzOperationalInsightsWorkspaceParams

Os seguintes exemplos de REST utilizam a operação da API REST do Workspaces . O plano tarifário está armazenado na propriedade sku do próprio espaço de trabalho.

Pagamento conforme utilização:

PATCH https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}?api-version={apiVersion}
Authorization: Bearer {accessToken}
Content-Type: application/json

{
  "properties": {
    "sku": {
      "name": "pergb2018"
    }
  }
}

Nível de compromisso:

PATCH https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}?api-version={apiVersion}
Authorization: Bearer {accessToken}
Content-Type: application/json

{
  "properties": {
    "sku": {
      "name": "capacityreservation",
      "capacityReservationLevel": <CapacityReservationInGb>
    }
  }
}

Os exemplos de Bicep seguintes utilizam o tipo de recurso Microsoft.OperationalInsights workspaces.

Pagamento conforme utilização:

param workspaceName string = '<WorkspaceName>'
param azureRegion string = '<AzureRegion>'

resource logAnalyticsWorkspace 'Microsoft.OperationalInsights/workspaces@<ApiVersion>' = {
  name: workspaceName
  location: azureRegion
  properties: {
    sku: {
      name: 'pergb2018'
    }
  }
}

Nível de compromisso:

param workspaceName string = '<WorkspaceName>'
param azureRegion string = '<AzureRegion>'
param capacityReservationInGb int

resource logAnalyticsWorkspace 'Microsoft.OperationalInsights/workspaces@<ApiVersion>' = {
  name: workspaceName
  location: azureRegion
  properties: {
    sku: {
      name: 'capacityreservation'
      capacityReservationLevel: capacityReservationInGb
    }
  }
}

Os seguintes exemplos de ARM (JSON) utilizam o tipo de recurso Microsoft.OperationalInsights workspaces.

Pagamento conforme utilização:

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "workspaceName": {
      "type": "string",
      "defaultValue": "<WorkspaceName>"
    },
    "azureRegion": {
      "type": "string",
      "defaultValue": "<AzureRegion>"
    }
  },
  "resources": [
    {
      "type": "Microsoft.OperationalInsights/workspaces",
      "apiVersion": "<ApiVersion>",
      "name": "[parameters('workspaceName')]",
      "location": "[parameters('azureRegion')]",
      "properties": {
        "sku": {
          "name": "pergb2018"
        }
      }
    }
  ]
}

Nível de compromisso:

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "workspaceName": {
      "type": "string",
      "defaultValue": "<WorkspaceName>"
    },
    "azureRegion": {
      "type": "string",
      "defaultValue": "<AzureRegion>"
    },
    "capacityReservationInGb": {
      "type": "int"
    }
  },
  "resources": [
    {
      "type": "Microsoft.OperationalInsights/workspaces",
      "apiVersion": "<ApiVersion>",
      "name": "[parameters('workspaceName')]",
      "location": "[parameters('azureRegion')]",
      "properties": {
        "sku": {
          "name": "capacityreservation",
          "capacityReservationLevel": "[parameters('capacityReservationInGb')]"
        }
      }
    }
  ]
}

Para saber como criar um teste de disponibilidade no portal do Azure, consulte Testes de disponibilidade do Application Insights.

O seguinte exemplo CLI do Azure utiliza o comando az monitor app-insights web-test create. Cria um teste de disponibilidade padrão com definições predefinidas.

# Set variables
resourceGroupName="<ResourceGroupName>"
resourceName="<ResourceName>"
azureRegion="<AzureRegion>"
webTestName="<WebTestName>"
requestUrl="<RequestUrl>"

# Get the subscription ID from the current Azure CLI context
subscriptionId=$(az account show --query id --output tsv)

# Create a standard availability test
az monitor app-insights web-test create \
  --resource-group "$resourceGroupName" \
  --location "$azureRegion" \
  --web-test-kind standard \
  --name "$webTestName" \
  --defined-web-test-name "$webTestName" \
  --request-url "$requestUrl" \
  --retry-enabled true \
  --ssl-check true \
  --ssl-lifetime-check 7 \
  --frequency 300 \
  --locations Id="us-ca-sjc-azr" \
  --locations Id="apac-sg-sin-azr" \
  --locations Id="us-il-ch1-azr" \
  --locations Id="us-va-ash-azr" \
  --locations Id="emea-au-syd-edge" \
  --http-verb GET \
  --timeout 120 \
  --expected-status-code 200 \
  --enabled true \
  --tags "hidden-link:/subscriptions/$subscriptionId/resourceGroups/$resourceGroupName/providers/microsoft.insights/components/$resourceName=Resource"

O exemplo Azure PowerShell seguinte utiliza o cmdlet New-AzApplicationInsightsWebTest. Cria um teste de disponibilidade padrão com definições predefinidas.

# Set variables
$resourceGroupName = "<ResourceGroupName>"
$resourceName = "<ResourceName>"
$azureRegion = "<AzureRegion>"
$webTestName = "<WebTestName>"
$requestUrl = "<RequestUrl>"

# Get the subscription ID from the current Azure PowerShell context
$subscriptionId = (Get-AzContext).Subscription.Id

# Define the geographic locations from which the web test is executed
$geoLocation = @()
$geoLocation += New-AzApplicationInsightsWebTestGeolocationObject -Location "us-ca-sjc-azr"
$geoLocation += New-AzApplicationInsightsWebTestGeolocationObject -Location "apac-sg-sin-azr"
$geoLocation += New-AzApplicationInsightsWebTestGeolocationObject -Location "us-il-ch1-azr"
$geoLocation += New-AzApplicationInsightsWebTestGeolocationObject -Location "us-va-ash-azr"
$geoLocation += New-AzApplicationInsightsWebTestGeolocationObject -Location "emea-au-syd-edge"

# Define parameters for New-AzApplicationInsightsWebTest
$newAzApplicationInsightsWebTestParams = @{
    ResourceGroupName              = $resourceGroupName
    Location                       = $azureRegion
    Name                           = $webTestName
    TestName                       = $webTestName
    Kind                           = "standard"
    RequestUrl                     = $requestUrl
    RetryEnabled                   = $true
    RuleSslCheck                   = $true
    RuleSslCertRemainingLifetimeCheck = 7
    Frequency                      = 300
    GeoLocation                    = $geoLocation
    RequestHttpVerb                = "GET"
    Timeout                        = 120
    RuleExpectedHttpStatusCode     = 200
    Enabled                        = $true
    Tag                            = @{
        "hidden-link:/subscriptions/$subscriptionId/resourceGroups/$resourceGroupName/providers/microsoft.insights/components/$resourceName" = "Resource"
    }
}

# Create a standard availability test
New-AzApplicationInsightsWebTest @newAzApplicationInsightsWebTestParams

O exemplo REST seguinte utiliza a operação da API REST Web Tests. Cria um teste de disponibilidade padrão com definições predefinidas.

PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Insights/webtests/{webTestName}?api-version={apiVersion}
Authorization: Bearer {accessToken}
Content-Type: application/json

{
  "location": "<AzureRegion>",
  "tags": {
    "hidden-link:/subscriptions/<SubscriptionId>/resourceGroups/<ResourceGroupName>/providers/microsoft.insights/components/<ResourceName>": "Resource"
  },
  "properties": {
    "Name": "<WebTestName>",
    "SyntheticMonitorId": "<WebTestName>",
    "Enabled": true,
    "Frequency": 300,
    "Timeout": 120,
    "Kind": "standard",
    "RetryEnabled": true,
    "Request": {
      "RequestUrl": "<RequestUrl>",
      "HttpVerb": "GET"
    },
    "ValidationRules": {
      "ExpectedHttpStatusCode": 200,
      "SSLCheck": true,
      "SSLCertRemainingLifetimeCheck": 7
    },
    "Locations": [
      { "Id": "us-ca-sjc-azr" },
      { "Id": "apac-sg-sin-azr" },
      { "Id": "us-il-ch1-azr" },
      { "Id": "us-va-ash-azr" },
      { "Id": "emea-au-syd-edge" }
    ]
  }
}

O exemplo Bicep seguinte utiliza o tipo de recurso Microsoft.Insights webtests. Cria um teste de disponibilidade padrão com definições predefinidas.

param subscriptionId string = '<SubscriptionId>'
param resourceGroupName string = '<ResourceGroupName>'
param resourceName string = '<ResourceName>'
param azureRegion string = '<AzureRegion>'
param webTestName string = '<WebTestName>'
param requestUrl string = '<RequestUrl>'

resource webTest 'Microsoft.Insights/webtests@<ApiVersion>' = {
  name: webTestName
  location: azureRegion
  tags: {
    'hidden-link:/subscriptions/${subscriptionId}/resourceGroups/${resourceGroupName}/providers/microsoft.insights/components/${resourceName}': 'Resource'
  }
  properties: {
    SyntheticMonitorId: webTestName
    Name: webTestName
    Enabled: true
    Frequency: 300
    Timeout: 120
    Kind: 'standard'
    RetryEnabled: true
    Locations: [
      { Id: 'us-ca-sjc-azr' }
      { Id: 'apac-sg-sin-azr' }
      { Id: 'us-il-ch1-azr' }
      { Id: 'us-va-ash-azr' }
      { Id: 'emea-au-syd-edge' }
    ]
    Request: {
      RequestUrl: requestUrl
      HttpVerb: 'GET'
    }
    ValidationRules: {
      ExpectedHttpStatusCode: 200
      SSLCheck: true
      SSLCertRemainingLifetimeCheck: 7
    }
  }
}

Para obter mais informações sobre como criar testes de disponibilidade usando o Bicep, consulte Microsoft.Insights webtests.

O seguinte exemplo de ARM (JSON) utiliza o Microsoft. Insights webtests tipo de recurso. Cria um teste de disponibilidade padrão com definições predefinidas.

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "subscriptionId": {
      "type": "string",
      "defaultValue": "<SubscriptionId>"
    },
    "resourceGroupName": {
      "type": "string",
      "defaultValue": "<ResourceGroupName>"
    },
    "resourceName": {
      "type": "string",
      "defaultValue": "<ResourceName>"
    },
    "azureRegion": {
      "type": "string",
      "defaultValue": "<AzureRegion>"
    },
    "webTestName": {
      "type": "string",
      "defaultValue": "<WebTestName>"
    },
    "requestUrl": {
      "type": "string",
      "defaultValue": "<RequestUrl>"
    }
  },
  "resources": [
    {
      "type": "Microsoft.Insights/webtests",
      "apiVersion": "<ApiVersion>",
      "name": "[parameters('webTestName')]",
      "location": "[parameters('azureRegion')]",
      "tags": {
        "[format('hidden-link:/subscriptions/{0}/resourceGroups/{1}/providers/microsoft.insights/components/{2}', parameters('subscriptionId'), parameters('resourceGroupName'), parameters('resourceName'))]": "Resource"
      },
      "properties": {
        "SyntheticMonitorId": "[parameters('webTestName')]",
        "Name": "[parameters('webTestName')]",
        "Enabled": true,
        "Frequency": 300,
        "Timeout": 120,
        "Kind": "standard",
        "RetryEnabled": true,
        "Locations": [
          { "Id": "us-ca-sjc-azr" },
          { "Id": "apac-sg-sin-azr" },
          { "Id": "us-il-ch1-azr" },
          { "Id": "us-va-ash-azr" },
          { "Id": "emea-au-syd-edge" }
        ],
        "Request": {
          "RequestUrl": "[parameters('requestUrl')]",
          "HttpVerb": "GET"
        },
        "ValidationRules": {
          "ExpectedHttpStatusCode": 200,
          "SSLCheck": true,
          "SSLCertRemainingLifetimeCheck": 7
        }
      }
    }
  ]
}

Para saber como criar um alerta de métrica no portal do Azure, consulte Tutorial: Criar um alerta de métrica para um recurso do Azure.

Para aprender a adicionar um alerta de métrica usando a CLI do Azure, consulte Criar uma nova regra de alerta usando a CLI, PowerShell ou um template ARM.

Para aprender a adicionar um alerta métrico usando o PowerShell, veja Criar uma nova regra de alerta usando a CLI, PowerShell ou um modelo ARM.

Para obter uma lista de vários exemplos de chamada de API REST para criar um alerta de métrica, consulte a documentação da API REST.

Para aprender a adicionar um alerta de métrica usando um modelo ARM, consulte Criar uma nova regra de alerta usando o CLI, PowerShell ou um template ARM.

Para aprender a adicionar um alerta de métrica usando um modelo ARM, consulte Criar uma nova regra de alerta usando o CLI, PowerShell ou um template ARM.