add Azure Monitor service doc

[HarshCasper]

Fixes DOC-79

[cloudflare-workers-and-pages]

Deploying localstack-docs with    Cloudflare Pages

Latest commit:	382b5da
Status:	✅  Deploy successful!
Preview URL:	https://14367bb7.localstack-docs.pages.dev
Branch Preview URL:	https://doc-79.localstack-docs.pages.dev

View logs

[paolosalvatori]

Hi @HarshCasper please review and integrate my comments, suggestions, and additions, thanks.

[paolosalvatori]

Suggested change

	These capabilities are useful for troubleshooting, auditing, and observability workflows.
	These capabilities are useful for troubleshooting, auditing, and observability workflows. For more information, see [Azure Monitor overview](https://learn.microsoft.com/azure/azure-monitor/fundamentals/overview).

[paolosalvatori]

Suggested change

	This reconfigures the `az` CLI to send commands to the official Azure management REST API. At this time, there is no full parity between `azlocal` and `az` commands after running `az start-interception`. Therefore, this technique is not fully interchangeable.
	This reconfigures the `az` CLI to send commands to the official Azure management REST API.

[paolosalvatori]

There is nothing wrong with stmonitordoc79, but it's better to use a simple name like mystore

Suggested change

	--name stmonitordoc79 \
	--name mystore \

[paolosalvatori]

Suggested change

	"id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-monitor-demo/providers/Microsoft.Storage/storageAccounts/stmonitordoc79",
	"id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-monitor-demo/providers/Microsoft.Storage/storageAccounts/mystore",

[paolosalvatori]

Following the recent refactoring, the fully qualified domain names (FQDN) for storage account endpoints have been updated.

Suggested change

	"blob": "https://stmonitordoc79blob.localhost.localstack.cloud:4566",
	"blob": "https://mystore.blob.core.azure.localhost.localstack.cloud:4566",

[paolosalvatori]

Suggested change

	"logs": [
	{
	"category": "Administrative",
	"enabled": true
	},
	{
	"category": "Security",
	"enabled": false
	}
	],
	"logs": [
	{
	"category": "StorageRead",
	"enabled": true,
	"retentionPolicy": {
	"days": 0,
	"enabled": false
	}
	},
	{
	"category": "StorageWrite",
	"enabled": true,
	"retentionPolicy": {
	"days": 0,
	"enabled": false
	}
	},
	{
	"category": "StorageDelete",
	"enabled": false,
	"retentionPolicy": {
	"days": 0,
	"enabled": false
	}
	}
	],
	"metrics": [
	{
	"category": "Transaction",
	"enabled": true,
	"retentionPolicy": {
	"days": 0,
	"enabled": false
	}
	},
	{
	"category": "Capacity",
	"enabled": true,
	"retentionPolicy": {
	"days": 0,
	"enabled": false
	}
	}
	],

[paolosalvatori]

Suggested change

	azlocal monitor diagnostic-settings delete \
	az monitor diagnostic-settings delete \

[paolosalvatori]

Suggested change

	--resource "$RESOURCE_ID"
	--resource "${RESOURCE_ID}/blobServices/default"

[paolosalvatori]

Suggested change

	## Features
	The Azure Monitor emulator supports the following features:
	- **Activity logs**: List activity log entries for a subscription, with optional filtering by resource ID and time range.
	- **Diagnostic settings**: Create, get, update, and delete diagnostic settings on any ARM resource.
	- **Application Insights components**: Create, get, update tags, list, delete, and purge Application Insights components. Billing features (get and update) are also supported.
	- **Action groups**: Create, get, update, list (by resource group or subscription), and delete action groups.
	- **Metric alerts**: Create, get, update, list (by resource group or subscription), and delete metric alert rules.
	- **Activity log alerts**: Create, get, update, list (by resource group or subscription), and delete activity log alert rules.
	- **Autoscale settings**: Create, get, update, list (by resource group or subscription), and delete autoscale settings.
	- **Scheduled query rules**: Create, get, update, list (by resource group or subscription), and delete scheduled query rules.
	- **Data collection rules and endpoints**: Create, get, update, list (by resource group or subscription), and delete data collection rules and data collection endpoints. Create, get, list (by resource, by rule, or by endpoint), and delete data collection rule associations.
	- **Web tests**: Create, get, update tags, list (by resource group, subscription, or component), and delete availability web tests.
	- **Workbooks and workbook templates**: Create, get, update, list (by resource group or subscription), and delete workbooks. Create, get, update, list (by resource group), and delete workbook templates. Workbook revisions (get and list) are also supported.
	- **Telemetry ingestion (data plane)**: Accept Application Insights SDK telemetry payloads (`track`), custom metrics publish, and live metrics subscription checks.
	- **Query API (data plane)**: Execute and get log analytics queries, retrieve metrics, and list events.
	## Limitations
	- **No data persistence across restarts**: Activity logs, diagnostic settings, and all resource state are held in memory and lost when the emulator is stopped or restarted.
	- **Activity log recording**: Only non-read (non-GET) control plane operations are recorded. Data plane operations and read requests do not produce activity log entries.
	- **Diagnostic settings are not enforced**: Diagnostic settings are stored but do not route logs or metrics to the specified destination (storage account, Log Analytics workspace, or event hub).
	- **Telemetry ingestion is a no-op**: The data plane telemetry endpoints (`track`, `publish`, `isSubscribed`) accept payloads and return success responses, but telemetry data is not stored or queryable.
	- **Query API returns empty results**: Log analytics queries, metrics, and event queries return structurally valid but empty responses.
	- **Autoscale rules are not evaluated**: Autoscale settings are stored but scaling actions are never triggered.
	- **Alert rule evaluation**: Metric alerts, activity log alerts, and scheduled query rules are stored as resources but are never evaluated or fired.
	- **Workbook revision history**: Revisions always return the current version of a workbook; historical revision tracking is not implemented.
	- **Components purge**: The purge endpoint accepts requests and returns an operation ID, but no data is actually purged.
	## Samples
	Explore the following samples to get started with Service Bus on LocalStack:
	- [Azure Functions App with Service Bus Messaging](https://github.com/localstack/localstack-azure-samples/blob/main/samples/function-app-service-bus/dotnet/)
	- [Azure Web App with Azure Cosmos DB for MongoDB](https://github.com/localstack/localstack-azure-samples/blob/main/samples/web-app-cosmosdb-mongodb-api/python/)

[paolosalvatori]

Suggested change

	Start your LocalStack container using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/).
	Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running:
	```bash
	azlocal start-interception
	```