Geomap panel not rendering map when sharing the screen onto a tv

Ask AI
1

We have a Geomap dashboard displaying locations across the map using hardcoded longitude and latitude coordinates from a SQL Server datasource . The data points (markers) render correctly in all scenarios however the basemap tiles fail to render under specific conditions.

What works:

  • Basemap renders correctly when viewing directly on the machine running Grafana

  • Basemap renders correctly on laptops and monitors accessing via the public dashboard link directly in a browser

  • Data points always render correctly in all scenarios since they are coordinate based

  • Panel opacity is set to 1

  • Map is centered correctly and zoom level is set

What doesn’t work:

  • The same laptop shows the basemap fine before screen sharing begins

  • The issue appears instantly when screen sharing starts

What we have tried:

  • Setting basemap opacity to 1

  • Switching between OpenStreetMap and CartoDB DarkMatter basemaps

  • Setting a fixed default map view with coordinates and zoom level

  • Using the public dashboard link instead of internal link

  • Hard refreshing the browser

Questions:

  1. Is there a way to force the basemap to render without WebGL so it survives screen sharing?

  2. Is there an alternative basemap provider that renders differently and might not be affected?

  3. Is there a Grafana setting to force software rendering as a fallback when hardware acceleration is unavailable?

  4. Has anyone else experienced this and found a reliable fix?

Environment:

  • Grafana accessed via public dashboard link

  • Chrome browser on Windows laptops

  • SQL Server datasource with hardcoded coordinates

  • Two data layers — running branches and branches with outages

1 Like
2

It sounds like you're encountering an issue where the basemap fails to render during screen sharing, likely due to how WebGL interacts with screen sharing software. Here are some suggestions and insights that might help address your questions:

  1. Force Basemap Rendering Without WebGL: Unfortunately, Grafana's geomap visualization relies heavily on WebGL for rendering, especially after the performance improvements introduced in Grafana 11.6. There isn't a built-in option to disable WebGL in Grafana itself. However, you can try disabling hardware acceleration in your browser settings, which might force the browser to use software rendering instead. In Chrome, you can do this by going to Settings > Advanced > System and toggling off "Use hardware acceleration when available."

  2. Alternative Basemap Providers: While switching between OpenStreetMap and CartoDB didn't resolve the issue, you might want to try using a custom XYZ tile server or MapLibre style layer, as these might behave differently. Ensure that the tile server you choose supports non-WebGL rendering, although this is more of a workaround than a guaranteed solution.

  3. Force Software Rendering: As mentioned, disabling hardware acceleration in the browser settings is the closest option to forcing software rendering. This setting is browser-specific and not controlled by Grafana.

  4. Community Experiences and Fixes: This issue might be specific to the combination of screen sharing software and WebGL. You could try using different screen sharing tools to see if the problem persists. Additionally, checking forums or community discussions for your specific screen sharing software might provide insights or updates on compatibility with WebGL.

If these suggestions don't resolve the issue, consider reaching out to the Grafana community or support for further assistance. They might have more specific insights or updates regarding this issue. Additionally, keeping your browser and Grafana instance updated can help, as newer versions might include fixes or improvements related to rendering and compatibility.

grot is still learning and improving, please let me know how I did by reacting below.

👍🏽 or 👎🏽

1 Like