Skip to content

Commit e95b2bd

Browse files
Update log-limitations.md
1 parent f60dc4f commit e95b2bd

1 file changed

Lines changed: 60 additions & 30 deletions

File tree

Lines changed: 60 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,50 +1,80 @@
11
---
2-
title: Log Emission and Diagnostic Settings Limitations for Partner Service Integration
3-
description: "Understand which Azure resources emit logs to the partner service, how to verify log emission, and the limitations of diagnostic settings for partner solutions."
2+
title: Troubleshoot log emission and diagnostic settings limitations for Azure partner service integration
3+
description: "Learn how to identify and resolve issues with log emission and diagnostic settings when integrating Azure resources with partner solutions."
44
author: ProfessorKendrick
55
ms.author: kkendrick
66
ms.service: partner-services
7-
ms.topic: troubleshooting-problem-resolution
7+
ms.topic: troubleshooting-general
88
ms.date: 08/04/2025
9-
ai-usage: ai-assisted
9+
10+
#customer intent: As an Azure administrator, I want to understand and resolve issues with log emission and diagnostic settings for partner service integrations so that I can ensure logs are properly sent and monitored.
11+
1012
---
1113

12-
# Log Emission and Diagnostic Settings Limitations for Partner Service Integration
14+
# Troubleshoot log emission and diagnostic settings limitations for Azure partner service integration
15+
16+
This article helps you identify and resolve issues that prevent Azure resources from emitting logs to partner services. It covers common causes, limitations of diagnostic settings, and steps to verify and correct configuration issues.
17+
18+
## Prerequisites
19+
20+
- Access to the Azure portal.
21+
- Sufficient permissions to view and modify diagnostic settings on Azure resources.
22+
- Knowledge of the partner solution integration requirements.
23+
24+
## Potential quick workarounds
25+
26+
1. Remove unused diagnostic settings if the resource has reached the maximum allowed.
27+
2. Confirm that the resource type supports diagnostic settings and log categories.
28+
29+
## Troubleshooting checklist
30+
31+
### Verify resource log support
32+
33+
- Navigate to the Azure portal and select the affected resource.
34+
- Go to **Diagnostic settings**.
35+
- Check if you can add a new diagnostic setting. If not, the resource may not support log emission.
36+
37+
### Check diagnostic settings limit
38+
39+
- Each Azure resource supports up to five diagnostic settings.
40+
- If you see an error about reaching the maximum, remove unused settings before adding new ones.
41+
42+
### Confirm metrics export limitation
43+
44+
- Metrics data export is not supported for partner solutions via Azure Monitor diagnostic settings. Only log data can be sent.
45+
46+
## Causes and/or solutions
47+
48+
### Cause: Resource does not support log emission
1349

14-
This article explains which Azure resources emit logs to the partner service, how to verify log emission, and the limitations of diagnostic settings for partner solutions.
50+
Some Azure resource types do not emit logs because they lack monitoring log categories.
1551

16-
## Symptoms
52+
**Solution:**
53+
1. Review the [Azure Monitor supported resource log categories](/azure/azure-monitor/essentials/resource-logs-categories).
54+
2. If your resource is not listed, it cannot emit logs to partner services.
1755

18-
- Logs are not appearing in the partner service as expected.
19-
- Unable to configure diagnostic settings for certain resources.
20-
- Error or warning about reaching the maximum number of diagnostic settings.
21-
- Metrics data is not exported to the partner service.
56+
### Cause: Diagnostic settings limit reached
2257

23-
## Cause
58+
Each resource can have a maximum of five diagnostic settings.
2459

25-
- Only resources listed in Azure Monitor resource log categories can emit logs to the partner service.
26-
- Some resource types do not support sending logs because they lack monitoring log categories.
27-
- Each Azure resource can have a maximum of five diagnostic settings.
28-
- Export of Metrics data is not currently supported by partner solutions under Azure Monitor diagnostic settings.
60+
**Solution:**
61+
1. Remove unused diagnostic settings from the resource.
62+
2. Add a new diagnostic setting for the partner service.
2963

30-
## Solution
64+
### Cause: Metrics data not exported
3165

32-
1. **Verify Resource Log Support:**
33-
- Navigate to the Azure diagnostic settings for the resource.
34-
- Check if a diagnostic setting option is available.
35-
- If not, the resource does not support sending logs.
66+
Export of metrics data is not currently supported for partner solutions.
3667

37-
2. **Check Diagnostic Settings Limit:**
38-
- Each resource can have up to five diagnostic settings.
39-
- If the limit is reached, remove unused settings before adding new ones.
68+
**Solution:**
69+
- Only log data can be sent to the partner service. No action is needed for metrics.
4070

41-
3. **Metrics Export Limitation:**
42-
- Metrics data export is not supported for partner solutions. Only log data can be sent to the partner service.
71+
## Advanced troubleshooting and data collection
4372

44-
> [!TIP]
45-
> For more information, see [Azure Monitor supported resource log categories](/azure/azure-monitor/essentials/resource-logs-categories) and [diagnostic settings documentation](/azure/azure-monitor/essentials/diagnostic-settings).
73+
- Collect screenshots of the diagnostic settings pane for the affected resource.
74+
- Note any error messages or warnings shown when configuring diagnostic settings.
75+
- Gather the resource type and region information for support escalation.
4676

4777
## Related content
4878

49-
- [Create diagnostic settings in Azure](/azure/azure-monitor/essentials/diagnostic-settings)
50-
-
79+
- [Azure Monitor supported resource log categories](/azure/azure-monitor/essentials/resource-logs-categories)
80+
- [Create diagnostic settings in Azure](/azure/azure-monitor/essentials/diagnostic-settings)

0 commit comments

Comments
 (0)