Azure Managed Grafana - PDF and Image Rendering

Hello @Javier Huamani

Thank you for contacting Microsoft Support regarding the dashboard rendering and PDF export behavior in Azure Managed Grafana.

We understand your concern regarding rendering performance, especially since your Azure Managed Grafana workspaces have already been upgraded to Grafana v13. We also understand that Grafana Labs has published performance improvements for PDF rendering in later Grafana releases, including demonstrations of exporting significantly larger dashboards.

Based on the current Microsoft documentation, Azure Managed Grafana uses Grafana's image rendering service to capture dashboard panels as images before generating PDF reports. Rendering is a CPU-intensive operation, and the service is currently subject to a maximum report-generation timeout of 200 seconds. Microsoft therefore recommends using dashboards with no more than 20 panels for PDF reporting workloads. If rendering exceeds the allowed limit, PDF generation may fail with an image rendering timeout error.

At this time, Microsoft has not publicly announced any roadmap or upcoming enhancements related to increasing the current rendering limits or supporting substantially larger dashboard exports within Azure Managed Grafana. As Azure Managed Grafana is a managed service, platform-specific resource limits and service configurations may differ from self-managed Grafana environments.

If your dashboards already contain fewer than 20 panels and are still experiencing rendering failures, we recommend performing the following troubleshooting steps:

1. Create a small test dashboard with 1-2 simple panels and attempt both PDF and image exports.

• If the test dashboard succeeds, the issue may be related to the original dashboard configuration, panels, or queries.
  1. Review panel query performance.
     • Verify that each panel loads successfully and that no queries are experiencing long execution times.
     • Slow data source responses can contribute to rendering timeouts.
     • Test different dashboard time ranges.
     • For example, attempt exports using the last 1 hour or 24 hours instead of longer periods to determine whether dataset size is contributing to the issue.
     • Identify whether a specific panel is causing failures.
     • Temporarily remove complex panels, large tables, transformations, or panels containing extensive historical data and retry the export.
     • Test different PDF layouts.
     • Attempt both portrait and landscape layouts and compare the results.
     • Validate whether the issue affects:
     • PDF export only
     • Image export only
     • Both PDF and image rendering
     • Test from an alternate browser or an InPrivate/Incognito session.
     • This helps eliminate browser cache or extension-related issues.
     • Review browser developer tools during export.
     • Capture any failed requests, HTTP errors, or rendering-related messages.
     • Verify whether the issue occurs across multiple Azure Managed Grafana workspaces.
     • If possible, test the same dashboard in another workspace to determine whether the behavior is workspace-specific.
     • Record the exact timestamp and error message when the failure occurs.
     • This information can be used for further backend investigation if required.

To assist with further analysis, please provide the following information:

• Azure Managed Grafana workspace name.
• Azure region where the workspace is deployed..
• Approximate number of panels in the affected dashboard.
• Whether the issue affects all dashboards or only specific dashboards.
• Timestamp (UTC) of the failed export.
• Screenshot of the error message.
• HAR trace collected during the failed export attempt.
• Confirmation of whether image exports experience the same behavior as PDF exports.

We apologize for the inconvenience and appreciate your patience. Once we receive the requested information, we will be happy to investigate further and determine whether the issue is related to dashboard complexity, query performance, rendering limitations, or a service-side issue requiring additional review.

Regards,

Microsoft Support Team.