-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
DigitalRCS edited this page Aug 5, 2026
·
1 revision
- Confirm the plugin directory name matches
digitalrcs-timeoverlay-panel. - Confirm
plugin.jsonandmodule.jsare directly inside that directory. - For an unsigned package, add the exact plugin ID to
allow_loading_unsigned_pluginsorGF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS. - Restart Grafana after installing the plugin or changing
plugin.json. - Search Grafana logs for
digitalrcs-timeoverlay-panel,unsigned, andsignature.
- Switch the Grafana query result to Table view and inspect the returned fields.
- Confirm at least one field is typed as Time and one as Number.
- For untyped tables, use a
timeor_timecolumn and numeric measurement values. - Use Grafana's Convert field type transformation if the datasource returned strings.
- Confirm the dashboard time picker includes the timestamps in the result.
- Define the CSV time field in the query schema and set it to Time.
- Leave Ignore unknown fields disabled for dynamic columns.
- Confirm the CSV datasource can access the configured file or URL from the Grafana server, not only from the user's browser.
- For local development, verify local-file access is explicitly enabled for the CSV plugin.
- Prefer timestamps with an explicit
Zor numeric timezone offset. - Configure the datasource timezone for timestamps without an offset.
- Confirm seconds-versus-milliseconds epoch units. Grafana transformations normally expect milliseconds; the panel fallback also recognizes common epoch-second values.
- Confirm its field is numeric after transformations.
- Check field filters and query transformations.
- Remove stale field-name overrides or update their matchers when dynamic series names change.
- Use a fixed-color field override when a series must always use the same color.
- Use Select for drag-to-zoom and Range for a persistent duration overlay.
- Zoom out cannot exceed the original dashboard time range; use Zoom all to restore it immediately.
- Select a range before using its edge handles or the delete control.
- Drag a note by its header; edit text in its body and resize it from the lower-right handle.
- Confirm the user has dashboard edit permission.
- Confirm the dashboard is not managed by file provisioning or another external provisioning system.
- Import editable dashboards through the Grafana API or create them through the UI.
- Confirm the renderer uses the same Grafana instance and can load the installed plugin assets.
- Confirm the dashboard was saved after editing overlays.
- Confirm the renderer can reach the datasource and receives the same time range.
- Test the exact production rendering or reporting service; browser screenshots alone do not validate server-side rendering.
Set another host port before starting Compose:
$env:GRAFANA_PORT = '3002'
docker compose up -dThe container continues to listen on port 3000 internally.
docker compose ps
docker compose logs --tail 300 grafana
curl.exe -fsS http://localhost:3001/api/healthDo not include passwords, API tokens, signing tokens, or sensitive datasource query results in issue reports.
DigitalRCS-TimeOverlay-Panel