Search Azure terms

Monitoring and Observability learning-path-anchor Telemetry events Telemetry events are breadcrumbs that say something meaningful happened in an application. They are different from raw logs because they usually have a clear event name and structured properties. A checkout completed, a document uploaded, a feature flag changed, or a device registered can all be telemetry events. In Azure Monitor Application Insights, these events help teams understand behavior, investigate incidents, and measure product outcomes. Good events are intentional, consistently named, and tied to the que Application data advanced 5 commands Aliases: event telemetry, custom events, Application Insights events, Azure Monitor events Quick peek Open full term page

Monitoring and Observability learning-path-anchor Throughput Throughput is the amount of work a system completes over time, such as requests, messages, bytes, events, or transactions per second. In Azure, teams measure it with service metrics, logs, and capacity settings to judge whether an app, database, storage account, or messaging pipeline can sustain demand. Performance intermediate 4 commands Aliases: Throughput, throughput, Azure Throughput, Microsoft Learn Throughput, requests per second, events per second, transactions per second, bytes per second, work completed over time Quick peek Open full term page

Monitoring and Observability premium Action group An Azure Monitor action group defines who gets notified and which actions run when an alert fires. It can include notification receivers such as email, SMS, and push, plus automation actions such as webhooks, secure webhooks, Azure Functions, Logic Apps, runbooks, ITSM, or Event Hubs. Alerts fundamentals 5 commands Aliases: Azure Monitor action group, alert action group, monitor action group Quick peek Open full term page

Monitoring and Observability premium Activity Log alert Activity Log alert is an Azure Monitor alert rule that fires when an Activity Log event matches defined conditions. In everyday Azure work, teams use it to notify responders when important Azure control-plane events happen, such as resource deletion, service health events, or privileged changes. The useful evidence is scope, condition fields, action group, enabled Azure Monitor alerts intermediate 4 commands Aliases: Azure Activity Log alert, management event alert, control-plane alert Quick peek Open full term page

Monitoring and Observability premium AI service diagnostic settings AI service diagnostic settings are Azure Monitor settings on an Azure AI or Foundry Tools resource that route resource logs and platform metrics to destinations such as Log Analytics, Storage, or Event Hubs for investigation and retention. Azure Monitor intermediate 3 commands Aliases: Azure AI diagnostic settings, Foundry Tools diagnostic logging, Cognitive Services diagnostic settings, AI resource logs Quick peek Open full term page

Monitoring and Observability premium Alert processing rule An alert processing rule is an Azure Monitor rule that modifies fired alerts, such as adding or suppressing action groups, applying filters, or using schedules without changing the alert rule itself. Azure Monitor Alerts fundamentals 3 commands Aliases: Azure Monitor alert processing rule, notification suppression rule, alert action rule Quick peek Open full term page

Monitoring and Observability premium Alert rule An alert rule is Azure Monitor configuration that watches a scope and signal, evaluates conditions, and creates alert instances when metric, log, activity, resource health, service health, or Prometheus criteria are met. Azure Monitor Alerts advanced 3 commands Aliases: Azure Monitor alert rule, monitoring rule, metric alert rule, log alert rule Quick peek Open full term page

Monitoring and Observability premium App role name An Application Insights telemetry value, also known as cloud role name, that identifies the logical application component shown in Application Map and related telemetry queries. It helps learners understand where the concept appears in Azure operations and what to verify before changing it. Telemetry fundamentals 2 commands Aliases: App role name, app role name, application insights role name, cloud role name, cloud_RoleName Quick peek Open full term page

Monitoring and Observability premium AppDependencies AppDependencies is the Azure Monitor Logs table used by Application Insights to store dependency telemetry for downstream calls such as HTTP services, SQL databases, storage, queues, and other remote components. Use it to reason about App Service behavior, validate configuration with CLI, and prevent hidden production impact from networking, scaling, recovery, security, or observability changes. Application Insights fundamentals 2 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability premium AppExceptions the Azure Monitor Logs table that stores exception telemetry collected from Application Insights-enabled applications. Application Insights table intermediate 2 commands Aliases: AppExceptions, appexceptions Quick peek Open full term page

Monitoring and Observability premium Application Insights connection string An Application Insights connection string specifies the Application Insights resource and endpoints that an instrumented application uses to send telemetry. Application Insights fundamentals 3 commands Aliases: APPLICATIONINSIGHTS_CONNECTION_STRING, application insights connection string Quick peek Open full term page

Monitoring and Observability premium Application map Application Map is an Application Insights view that visualizes application components and dependencies using telemetry, helping teams identify bottlenecks and failure hotspots. Application Insights fundamentals 2 commands Aliases: application map Quick peek Open full term page

Monitoring and Observability premium AppRequests AppRequests is an Azure Monitor Logs table for Application Insights request telemetry, including request duration, result code, success state, operation, and related application context. Application Insights table fundamentals 2 commands Aliases: Application Insights requests table, apprequests Quick peek Open full term page

Monitoring and Observability premium AppTraces AppTraces is the Azure Monitor table where Application Insights stores trace and log messages emitted by an application. In plain terms, it is where developers and operators look for the app’s own words during troubleshooting. Requests and dependencies explain what happened around the app, but traces often explain what the code thought it. Application Insights table intermediate 2 commands Aliases: Application Insights traces, traces table, Azure Monitor AppTraces, trace telemetry table Quick peek Open full term page

Monitoring and Observability premium Availability result Availability result is the recorded outcome of an Application Insights availability test run, including whether the probe succeeded, how long it took, and where it ran. In Azure, teams encounter it when teams query Azure Monitor Logs after a synthetic web test reports failures, slow responses, or regional differences. The useful question is what behavior Availability intermediate 4 commands Aliases: AppAvailabilityResults, availability test result, Application Insights availability result Quick peek Open full term page

Monitoring and Observability premium Availability test Availability test is an outside-in monitor that repeatedly calls a public HTTP or HTTPS endpoint and records whether it responded quickly enough. In Azure, teams encounter it when product teams need synthetic checks for websites, APIs, or critical external dependencies before users report an outage. The useful question is what behavior it proves, who owns Availability intermediate 4 commands Aliases: Application Insights availability test, web test, standard test, synthetic test Quick peek Open full term page

Monitoring and Observability premium Azure dashboard A customizable Azure portal view for organizing resource tiles, metrics, charts, links, and operational context into private or shared dashboards. Visualization fundamentals 4 commands Aliases: Azure portal dashboard, Portal dashboard Quick peek Open full term page

Monitoring and Observability premium Azure Monitor Azure Monitor is Microsoft’s unified observability service for collecting, analyzing, and acting on telemetry from Azure, hybrid, and application workloads. It brings together metrics, logs, traces, events, alerts, workbooks, and Application Insights capabilities so teams can understand health, performance, and reliability. Monitoring fundamentals 3 commands Aliases: Azure Monitor, Monitor, Azure observability, Log Analytics, Application Insights, Azure metrics and logs Quick peek Open full term page

Monitoring and Observability premium Azure Resource Health Azure Resource Health reports current and past health for individual Azure resources and helps diagnose service-impacting problems. Operational hygiene fundamentals 5 commands Aliases: Azure Resource Health, Azure resource health status, Resource Health, resource availability status Quick peek Open full term page

Monitoring and Observability premium Browser telemetry Browser telemetry is client-side performance and usage data collected from web browsers, commonly through the Application Insights JavaScript SDK in Azure Monitor. Frontend performance advanced 3 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability premium Change Analysis Change Analysis helps identify changes that may have affected application or resource behavior. Operational hygiene fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability premium Correlation ID A correlation ID links telemetry records that belong to the same request, operation, or transaction. Tracing fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability premium Cumulative Layout Shift a web performance metric that measures how much visible page content unexpectedly moves while a user is trying to read or interact. Web performance advanced 3 commands Aliases: CLS, Core Web Vitals CLS, layout shift metric Quick peek Open full term page

Monitoring and Observability premium Database diagnostic settings Azure Monitor routing rules that export database logs and metrics to Log Analytics, Storage, Event Hubs, or partner destinations for investigation and governance. Azure Monitor intermediate 4 commands Aliases: SQL diagnostic settings, database diagnostics export, Azure Monitor diagnostic settings for databases Quick peek Open full term page

Monitoring and Observability premium Diagnostic setting A diagnostic setting is an Azure Monitor configuration that routes platform logs and metrics from a resource to supported destinations such as Log Analytics, Event Hubs, or Storage. Diagnostics fundamentals 4 commands Aliases: Azure Monitor diagnostic setting, resource diagnostic setting, platform log routing, diagnostic settings Quick peek Open full term page

Monitoring and Observability premium Diagnostic settings for storage Diagnostic settings for storage route Azure Storage platform logs and metrics, including service-specific operations where supported, to destinations such as Log Analytics, Event Hubs, or Storage for investigation and compliance. Data operations intermediate 4 commands Aliases: storage diagnostic settings, Azure Storage diagnostic settings, Storage account diagnostic settings, storage platform log routing Quick peek Open full term page

Monitoring and Observability premium Diagnostic settings policy A diagnostic settings policy is an Azure Policy definition or initiative that audits, denies, or deploys diagnostic settings at scale so supported resources send logs and metrics to approved destinations. Governance operations intermediate 4 commands Aliases: Azure Policy for diagnostic settings, diagnostic settings Azure Policy, policy-based diagnostic settings, deploy diagnostic settings policy Quick peek Open full term page

Monitoring and Observability premium Distributed tracing Distributed tracing follows a request across services, dependencies, and process boundaries so teams can understand latency, failures, and call relationships in a distributed application. Application telemetry intermediate 4 commands Aliases: end-to-end tracing, OpenTelemetry tracing, application distributed trace, transaction trace Quick peek Open full term page

Monitoring and Observability premium Error budget An error budget is the amount of unreliability a service can consume while still meeting its service level objective over a defined measurement window. SRE and reliability intermediate 4 commands Aliases: error budget Quick peek Open full term page

Monitoring and Observability premium Error rate Error rate is the proportion of requests, operations, or events that fail compared with the total volume over a defined time window. Metrics and SRE fundamentals 4 commands Aliases: error rate Quick peek Open full term page

Monitoring and Observability premium HTTP 4xx HTTP 4xx refers to client error responses, such as unauthorized, forbidden, not found, or bad request, observed by Azure applications and monitoring tools. HTTP operations intermediate 4 commands Aliases: HTTP 4xx, http 4xx Quick peek Open full term page

Monitoring and Observability premium HTTP 5xx HTTP 5xx refers to server error responses that indicate an application, platform component, gateway, or downstream dependency failed to handle a request. HTTP operations intermediate 4 commands Aliases: HTTP 5xx, http 5xx Quick peek Open full term page

Monitoring and Observability premium HTTP queue length HTTP queue length is an App Service plan metric that shows the average number of HTTP requests waiting in the queue before being fulfilled. Azure App Service intermediate 5 commands Aliases: HTTP queue length, http queue length Quick peek Open full term page

Monitoring and Observability premium Instrumentation key Instrumentation key controls which Application Insights component receives telemetry and how older application configurations identify the target monitoring resource. Teams see it in application insights resource properties, app settings. It is not a secret access key, API key, SAS token, Log Analytics workspace ID, or managed identity credential; confusing them can create missing telemetry, cross-environment data pollution. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Application Insights Fundamentals 5 commands Aliases: ikey, Application Insights instrumentation key, AI instrumentation key, telemetry instrumentation key Quick peek Open full term page

Monitoring and Observability premium Interaction to Next Paint Interaction to Next Paint controls how teams measure whether web pages feel responsive after real user interactions, especially for Azure-hosted web apps and customer portals. Teams see it in microsoft edge devtools, microsoft clarity dashboards. It is not server response time, Time to First Byte, First Input Delay, Cumulative Layout Shift, or a backend CPU metric; confusing them can create slow clicks, abandoned checkout flows. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Web Vitals Intermediate 5 commands Aliases: INP, Core Web Vitals INP, web responsiveness metric, interaction responsiveness Quick peek Open full term page

Monitoring and Observability premium KQL KQL controls how operators search telemetry, detect incidents, investigate performance, build dashboards, create alerts, and summarize operational evidence across Azure services. Teams see it in log analytics workspaces, azure monitor logs. It is not SQL, PromQL, OData filters, ARM template expressions, Azure Data Factory expression language, or application code; confusing them can create missed incidents, expensive queries. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Query language Fundamentals 5 commands Aliases: Kusto Query Language, Kusto query, Azure Monitor query language, Sentinel query language Quick peek Open full term page

Monitoring and Observability premium KQL function KQL function controls how teams reuse common filters, joins, calculations, detections, and normalization logic across monitoring, security, and analytics workloads. Teams see it in azure data explorer databases, microsoft sentinel hunting queries. It is not an Azure Function app, SQL stored procedure, Logic Apps workflow, user-defined scalar operator, or ARM template function; confusing them can create stale detection logic, broken dashboards. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Query language Intermediate 5 commands Aliases: Kusto function, user-defined KQL function, stored Kusto function, query-defined function Quick peek Open full term page

Monitoring and Observability premium Log Analytics table A Log Analytics table is the named storage structure inside a Log Analytics workspace that holds one kind of Azure Monitor log record, with its own schema, plan, retention behavior, access considerations, and KQL query patterns for troubleshooting, analytics, and compliance. Azure Monitor Logs fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability premium Log Analytics workspace A Log Analytics workspace is the Azure Monitor Logs data store where collected log records are retained, secured, queried with KQL, and used by alerts, workbooks, Microsoft Sentinel, Application Insights, and operations teams to troubleshoot and govern Azure workloads in governed production environments. Azure Monitor Logs fundamentals 4 commands Aliases: workspace, LAW Quick peek Open full term page

Monitoring and Observability premium Metric alert Metric alert is an Azure Monitor alert rule that watches one or more metrics and triggers action when the configured condition is met. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Azure Monitor Alerts advanced 4 commands Aliases: Azure Monitor metric alert, metric alert rule, metric-based alert Quick peek Open full term page

Monitoring and Observability premium Metric dimension Metric dimension is a property attached to metric data that lets Azure Monitor split, filter, or group the same metric by useful values. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Azure Monitor Metrics fundamentals 4 commands Aliases: metric split, metric label, dimension value Quick peek Open full term page

Monitoring and Observability premium Metric namespace Metric namespace is a category container that groups related Azure Monitor metrics for a resource type or service. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Azure Monitor Metrics fundamentals 4 commands Aliases: metrics namespace, metric category, Azure Monitor metric namespace Quick peek Open full term page

Monitoring and Observability premium Metric time grain Metric time grain is the time interval Azure Monitor uses to aggregate metric samples for charts, queries, or alert evaluation. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Azure Monitor Metrics fundamentals 4 commands Aliases: metric granularity, time grain, aggregation interval Quick peek Open full term page

Monitoring and Observability premium Platform metrics Platform metrics are numeric measurements that Azure resources emit and Azure Monitor collects at regular intervals. They describe resource health, capacity, utilization, latency, throughput, failures, and dimensions over time, helping operators chart behavior, create alerts, and diagnose service conditions quickly. Monitoring fundamentals 5 commands Aliases: Azure platform metrics, Azure Monitor platform metrics, resource metrics Quick peek Open full term page

Monitoring and Observability premium Search service diagnostic logs Search service diagnostic logs are Azure Monitor resource logs from Azure AI Search that record query, suggest, autocomplete, lookup, indexing, service statistics, and operational events. They are collected in Log Analytics or storage when diagnostic settings are enabled on the search service. Data operations intermediate 5 commands Aliases: Azure AI Search logs, search resource logs, Microsoft.Search diagnostics, search operation logs, Search diagnostic settings Quick peek Open full term page

Monitoring and Observability premium Service Health alert A Service Health alert is an Azure Monitor activity log alert that watches ServiceHealth events for selected subscriptions, regions, and services. It routes incident, planned maintenance, security, or health advisory notifications to action groups so teams learn about platform issues before users report symptoms. Operational hygiene intermediate 5 commands Aliases: Azure Service Health alert, Service Health alert, ServiceHealth activity log alert, platform health alert, service health alert, service-health-alert Quick peek Open full term page

Monitoring and Observability verified Data collection endpoint An Azure Monitor resource that provides regional endpoints used by agents and data collection rules for configuration access and telemetry ingestion. Azure Monitor data collection Intermediate 4 commands Aliases: DCE, Azure Monitor DCE, monitor data collection endpoint Quick peek Open full term page

Monitoring and Observability verified Data collection rule An Azure Monitor resource that defines what telemetry to collect, how to transform it, and where to send it. Azure Monitor data collection Intermediate 4 commands Aliases: DCR, Azure Monitor DCR, monitor collection rule Quick peek Open full term page

Monitoring and Observability field-manual-complete Largest Contentful Paint Largest Contentful Paint is a web performance metric that measures how quickly the largest visible content element in the viewport finishes rendering. Microsoft guidance treats it as a loading-experience signal, commonly associated with Core Web Vitals and a target of about 2.5 seconds for good user experience. Web Vitals advanced 2 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability field-manual-complete Latency Latency is the time delay between a request, event, or operation starting and the useful result becoming available. In Azure, Microsoft Learn discusses latency through metrics, Application Insights durations, dependency calls, ingestion delay, performance monitoring, and architecture choices that affect user experience and operational response. Performance intermediate 2 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability field-manual-complete Live Metrics Microsoft Learn describes Live Metrics in Application Insights as real-time monitoring for web applications. It lets teams watch selected metrics and performance counters live, filter telemetry, and inspect sample failed requests or exceptions while an application is running. Application Insights fundamentals 2 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability verified P50 P50 is the 50th percentile, or median, of a measured population such as request latency. In Azure monitoring and Kusto queries, percentile metrics show the value at or below which a percentage of samples fall, helping teams compare typical experience with tail behavior. Performance intermediate 4 commands Aliases: 50th percentile, median latency, median percentile, p50 latency Quick peek Open full term page

Monitoring and Observability verified P95 P95 is the 95th percentile of a measured population such as request latency. In Azure monitoring and Kusto queries, it shows the value at or below which 95 percent of samples fall, making it useful for tail-latency analysis and workload performance objectives. Performance intermediate 4 commands Aliases: 95th percentile, tail latency, p95 latency, 95 percentile latency Quick peek Open full term page

Monitoring and Observability verified P99 P99 is the 99th percentile of a measured set, such as request duration or dependency latency. In Azure monitoring and Kusto queries, it shows the value at or below which 99 percent of samples fall, helping teams examine extreme tail behavior. Performance telemetry intermediate 4 commands Aliases: 99th percentile, p99 latency, tail percentile, extreme tail latency Quick peek Open full term page

Monitoring and Observability verified Workspace retention Workspace retention defines how long Log Analytics data remains available for analytics and how long it is kept in long-term retention. Retention can be configured at workspace and table levels, affecting query availability, search jobs, compliance evidence, incident review, and Azure Monitor storage cost before data is deleted. Logs fundamentals 5 commands Aliases: Log Analytics retention, Workspace data retention, Azure Monitor Logs retention, Table retention Quick peek Open full term page

Monitoring and Observability top-250-pre130-priority-upgraded Activity Log Activity Log is a subscription-level record of Azure control-plane events such as resource create, update, delete, policy, service-health, alert, and administrative actions in Azure. Azure Monitor fundamentals 4 commands Aliases: Azure Activity Log, Azure Monitor Activity Log, control-plane log, Activity Log Quick peek Open full term page

Monitoring and Observability field-manual-ready Monitoring Reader Monitoring Reader is an Azure role that lets users view monitoring data and settings without broad resource management permissions. Azure Monitor RBAC fundamentals 4 commands Aliases: Azure Monitor Reader, Monitoring Reader, monitoring RBAC Quick peek Open full term page

Monitoring and Observability template-specs-upgraded Sampling Sampling keeps a representative share of telemetry so diagnostics remain useful without sending every trace, dependency, request, or log to Azure Monitor. Telemetry fundamentals 3 commands Aliases: Application Insights sampling, telemetry sampling, OpenTelemetry sampling, fixed-rate sampling, rate-limited sampling Quick peek Open full term page

Monitoring and Observability template-specs-upgraded Scheduled query alert A scheduled query alert is an Azure Monitor alert built from a KQL query that runs again and again on a defined cadence. Monitoring advanced 6 commands Aliases: log search alert, Azure Monitor scheduled query rule, scheduledQueryRules, KQL alert, Log Analytics alert Quick peek Open full term page

Monitoring and Observability complete SLA A formal availability commitment for an Azure service or configuration, separate from the workload SLO users actually experience. Reliability fundamentals 5 commands Aliases: service-level agreement, service level agreement, Azure SLA, availability commitment Quick peek Open full term page

Monitoring and Observability complete SLO Microsoft Learn reliability guidance treats a service-level objective as a measurable target for how well a workload should serve users, usually expressed through availability, latency, error rate, or another service-level indicator. In Azure, SLOs are implemented through monitoring, alerts, dashboards, and error-budget decisions rather than as one standalone resource. Reliability fundamentals 2 commands Aliases: Service-level objective, Service level objective, reliability objective, error budget target Quick peek Open full term page