Resource monitor

BMC AMI Ops resources are identified to an ESM by a resource class name and entity name.Class nameThe default security class for resources in windows mode is $BBM. By default, $BBM is transformed (by use of a NEXT statement) to external resource class FACILITY, which is a predefined class for CA-ACF2, CA-Top Secret, and RACF.For information about using a class other than FACILITY, see Class-definitions.Entity namesAll BMC AMI Ops resources in windows mode (such as view data and actions) have a defined resource entity name.BMC AMI Ops resource entity names consist of multiple qualifiers separated by periods, similar to data set names. The format of a resource entity name is:BBM.product.context.internalID.suffixParameterDescriptionBBMIs the prefix for all BMC AMI Ops resourcesproductIs the ID of the product or service point that is in control of the window where the resource is being accessedFor a list of product IDs, see Product IDs for resource entity names in windows mode.contextIs the context that is set in the window where the resource is being accessedinternalIDIs the internal ID of the data table or action that is being accessedsuffixIndicates the type of resource that is being accessedFor a list of resource entity name suffixes, see Suffixes for resource entity names in windows mode.The following lists of BMC AMI Ops product IDs that can be part of a resource entity name.Product IDs for resource entity names in windows modeProduct IDProduct or service pointCMFBMC AMI Ops Monitor for CMFCOMMONCommon BMC AMI Ops resourcesICAPBMC AMI Ops Automation for CappingMVALERTAlarm ManagementMVAOBMC AMI Ops AutomationMVCICSBMC AMI Ops Monitor for CICSMVCSMONCOMMON STORAGE MONITORMVDB2BMC AMI Ops Monitor for Db2MVEXPMainView ExplorerMVIMSBMC AMI Ops Monitor for IMS Online and BMC AMI Ops Monitor for DBCTLMVIPBMC AMI Ops Monitor for IPMVJEMainView for Java EnvironmentsMVMQSBMC AMI Ops Monitor for MQMVMVSBMC AMI Ops Monitor for z/OSMVSPSBMC AMI Ops SYSPROG ServicesMVSRMBMC AMI Storage commonMVSRMHSMBMC AMI Storage EasyHSMMVSRMSGCBMC AMI Storage ApplicationsMVSRMSGDBMC AMI Storage Space HistoryMVSRMSGPBMC AMI Storage Performance HistoryMVTAMainView Transaction AnalyzerMVTOMTotal Object ManagerMVUSSBMC AMI Ops Monitor for UNIX System ServicesMVVPMainView VistaPointMVVTAMMainView for VTAMMVWEBMainView for WebSphere Application ServerPLEXMGRBMC AMI Ops Plex ManagerThe following lists of the resource suffixes that can be part of a resource entity name.Suffixes for resource entity names in windows modeSuffixResource typeAAAny action for a given productAOAny action on the current table of dataCNConnection to a CAS, which provides access to the BMC AMI Ops environmentOAAny action on an object in a table, such as a row of dataODTable data and the views that display the dataPAAny product-level (or primary) actionPFA product-level functionPSA product-level service or agent activityTAAccess to a target context, which controls access to a product from the BMC AMI Ops Selection MenuTCCreation of a target context, which allows an address space to define itself as a productTHSetting

Be associated with more than one resource type.For more information about the resource types for SQL Database, see SQL Database monitoring data reference.Data storageFor Azure Monitor:Metrics data is stored in the Azure Monitor metrics database.Log data is stored in the Azure Monitor logs store. Log Analytics is a tool in the Azure portal that can query this store.The Azure activity log is a separate store with its own interface in the Azure portal.You can optionally route metric and activity log data to the Azure Monitor logs store. You can then use Log Analytics to query the data and correlate it with other log data.Many services can use diagnostic settings to send metric and log data to other storage locations outside Azure Monitor. Examples include Azure Storage, hosted partner systems, and non-Azure partner systems, by using Event Hubs.For detailed information on how Azure Monitor stores data, see Azure Monitor data platform.Azure Monitor platform metricsAzure Monitor provides platform metrics for most services. These metrics are:Individually defined for each namespace.Stored in the Azure Monitor time-series metrics database.Lightweight and capable of supporting near real-time alerting.Used to track the performance of a resource over time.Collection: Azure Monitor collects platform metrics automatically. No configuration is required.Routing: You can also route some platform metrics to Azure Monitor Logs / Log Analytics so you can query them with other log data. Check the DS export setting for each metric to see if you can use a diagnostic setting to route the metric to Azure Monitor Logs / Log Analytics.For more information, see the Metrics diagnostic setting.To configure diagnostic settings for a service, see Create diagnostic settings in Azure Monitor.For a list of all metrics it's possible to gather for all resources in Azure Monitor, see Supported metrics in Azure Monitor.Azure SQL Database metricsYou can use metrics to monitor database and elastic pool resource consumption and health. For example, you can:Right-size the database or elastic pool to your application workloadDetect a gradual increase in resource consumption, and proactively scale up the database or elastic poolDetect and troubleshoot a performance problemFor a list and descriptions of commonly used metrics in Azure SQL Database, see Azure SQL Database metrics.For tables of all available metrics for SQL Database, see SQL Database monitoring data reference.Azure Monitor resource logsResource logs provide insight into operations that were done by an Azure resource. Logs are generated automatically, but you must route them to Azure Monitor logs to save or query them. Logs are organized in categories. A given namespace might have multiple resource log categories.Collection: Resource logs aren't collected and stored until you create a diagnostic setting and route the logs to one or more locations. When you create a diagnostic setting, you specify which categories of logs to collect. There are multiple ways to create and maintain diagnostic settings, including the Azure portal, programmatically, and though Azure Policy.Routing: The suggested default is to route resource logs to Azure Monitor Logs so you can query them with other log data. Other locations such as Azure Storage,

Azure Event Hubs, and certain Microsoft monitoring partners are also available. For more information, see Azure resource logs and Resource log destinations.For detailed information about collecting, storing, and routing resource logs, see Diagnostic settings in Azure Monitor.For a list of all available resource log categories in Azure Monitor, see Supported resource logs in Azure Monitor.All resource logs in Azure Monitor have the same header fields, followed by service-specific fields. The common schema is outlined in Azure Monitor resource log schema.Azure SQL Database logsAuditing for Azure SQL Database tracks database events and writes them to an audit log in your Azure storage account, Log Analytics workspace, or Event Hubs. For more information, see Auditing for Azure SQL Database.For more information on the resource logs and diagnostics available for Azure SQL Database, see Configure streaming export of diagnostic telemetry.For the available resource log categories, their associated Log Analytics tables, and the log schemas for SQL Database, see SQL Database monitoring data reference.Azure activity logThe activity log contains subscription-level events that track operations for each Azure resource as seen from outside that resource; for example, creating a new resource or starting a virtual machine.Collection: Activity log events are automatically generated and collected in a separate store for viewing in the Azure portal.Routing: You can send activity log data to Azure Monitor Logs so you can analyze it alongside other log data. Other locations such as Azure Storage, Azure Event Hubs, and certain Microsoft monitoring partners are also available. For more information on how to route the activity log, see Overview of the Azure activity log.Analyze monitoring dataThere are many tools for analyzing monitoring data.Azure Monitor toolsAzure Monitor supports the following basic tools:Metrics explorer, a tool in the Azure portal that allows you to view and analyze metrics for Azure resources. For more information, see Analyze metrics with Azure Monitor metrics explorer.Log Analytics, a tool in the Azure portal that allows you to query and analyze log data by using the Kusto query language (KQL). For more information, see Get started with log queries in Azure Monitor.The activity log, which has a user interface in the Azure portal for viewing and basic searches. To do more in-depth analysis, you have to route the data to Azure Monitor logs and run more complex queries in Log Analytics.Tools that allow more complex visualization include:Dashboards that let you combine different kinds of data into a single pane in the Azure portal.Workbooks, customizable reports that you can create in the Azure portal. Workbooks can include text, metrics, and log queries.Grafana, an open platform tool that excels in operational dashboards. You can use Grafana to create dashboards that include data from multiple sources other than Azure Monitor.Power BI, a business analytics service that provides interactive visualizations across various data sources. You can configure Power BI to automatically import log data from Azure Monitor to take advantage of these visualizations.Azure Monitor export toolsYou can get data out of Azure Monitor into other tools by using the following methods:Metrics: Use the

Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Monitor Azure SQL Database Article08/23/2024 In this article -->Applies to: Azure SQL DatabaseThis article describes:The types of monitoring data you can collect for this service.Ways to analyze that data.NoteIf you're already familiar with this service and/or Azure Monitor and just want to know how to analyze monitoring data, see the Analyze section near the end of this article.When you have critical applications and business processes that rely on Azure resources, you need to monitor and get alerts for your system. The Azure Monitor service collects and aggregates metrics and logs from every component of your system. Azure Monitor provides you with a view of availability, performance, and resilience, and notifies you of issues. You can use the Azure portal, PowerShell, Azure CLI, REST API, or client libraries to set up and view monitoring data.For more information on Azure Monitor, see the Azure Monitor overview.For more information on how to monitor Azure resources in general, see Monitor Azure resources with Azure Monitor.The SQL Server database engine has its own monitoring and diagnostic capabilities that Azure SQL Database uses, such as Query Store and dynamic management views (DMVs). For more information, see Monitor performance by using the Query Store and Monitor Azure SQL Database performance using dynamic management views.For a detailed discussion of all monitoring and performance aspects of Azure SQL Database and Azure SQL Managed Instance, see Monitor and performance tuning in Azure SQL Database and Azure SQL Managed Instance.Database watcher (preview)Database watcher collects in-depth workload monitoring data to give you a detailed view of database performance, configuration, and health. Dashboards in the Azure portal provide a single-pane-of-glass view of your Azure SQL estate and a detailed view of each monitored resource. Data is collected into a central data store in your Azure subscription. You can query, analyze, export, visualize collected data and integrate it with downstream systems.For more information about database watcher, see the following articles:Monitor Azure SQL workloads with database watcher (preview)Quickstart: Create a database watcher to monitor Azure SQL (preview)Create and configure a database watcher (preview)Database watcher data collection and datasets (preview)Analyze database watcher monitoring data (preview)Database watcher FAQQuery performance insightQuery performance insight uses the SQL Server Query Store to provide intelligent query analysis and insight on query plan choice and performance for single and pooled databases. For more information, see Query Performance Insight for Azure SQL Database.Resource typesAzure uses the concept of resource types and IDs to identify everything in a subscription. Resource types are also part of the resource IDs for every resource running in Azure. For example, one resource type for a virtual machine is Microsoft.Compute/virtualMachines. For a list of services and their associated resource types, see Resource providers.Azure Monitor similarly organizes core monitoring data into metrics and logs based on resource types, also called namespaces. Different metrics and logs are available for different resource types. Your service might

10% CPU. This comes in handy when scaling your cluster, or optimizing your application's processes.Can I predict infrastructure issues proactively? - many issues are preceded by sudden changes (drops) in performance, so you can use performance counters such as network I/O and CPU utilization to predict and diagnose the issues proactively.A list of performance counters that should be collected at the infrastructure level can be found at Performance metrics.Azure Monitor Logs is recommended for monitoring cluster level events. After you configure the Log Analytics agent with your workspace, you can collect:Performance metrics such as CPU utilization..NET performance counters such as process level CPU utilization.Service Fabric performance counters such as number of exceptions from a reliable service.Container metrics such as CPU utilization.Resource typesAzure uses the concept of resource types and IDs to identify everything in a subscription. Resource types are also part of the resource IDs for every resource running in Azure. For example, one resource type for a virtual machine is Microsoft.Compute/virtualMachines. For a list of services and their associated resource types, see Resource providers.Azure Monitor similarly organizes core monitoring data into metrics and logs based on resource types, also called namespaces. Different metrics and logs are available for different resource types. Your service might be associated with more than one resource type.For more information about the resource types for Azure Service Fabric, see Service Fabric monitoring data reference.Data storageFor Azure Monitor:Metrics data is stored in the Azure Monitor metrics database.Log data is stored in the Azure Monitor logs store. Log Analytics is a tool in the Azure portal that can query this store.The Azure activity log is a separate store with its own interface in the Azure portal.You can optionally route metric and activity log data to the Azure Monitor logs store. You can then use Log Analytics to