Skip to content

Latest commit

 

History

History
107 lines (78 loc) · 4.58 KB

troubleshooting.md

File metadata and controls

107 lines (78 loc) · 4.58 KB

Troubleshooting the Grafana-PRTG Plugin

Taking note of issues I run into!

Values Don’t Quite Match Up

Check the timing in the top right (of the dashboard).

Set the quick range to Last 5 Minutes. Make sure that the Value Stat is set to Current (under Visualization), as it defaults to Average

l is undefined (multiple causes)

I first encountered this when I added a device to a group that was running a graph.

Cause 1:

  • (In PRTG) Device/Sensor Settings > Scanning Interval: 4 hours

Why it Caused the Map to Return as Undefined:

  • The dashboard (Grafana) is set to pull data from the last 6 hours

Fix:

  • Adjust either the PRTG scanning interval or how long the dashboard goes back
  • Changes won't be immediate; log out of the dashboard/clear cookies and/or trigger a sensor scan on PRTG (click the two arrows or the chevron > Scan Now)

Not sure why this didn't gracefully fail and grey out the particular sensor object.. bug in either the plugin/Grafana, perhaps. Though its worth noting on the TV Display (Pi that runs throughout the night), I did see a similar object greyed out on the same graph during the morning.

The instance that prompted me to take note of this was triggered while adding new devices and viewing on my PC, so plausibly a cache bug. I suspect the same warning appeared on the Pi, but no one was around to see it. By the time it was seen, the cache was created? Not enough info to submit a bug report, yet.

Cause 2:

  • A device (or sensor) in the target group is paused

Fix:

  • Unpause (or remove the device from the group)
  • Refresh the dashboard

Unclear if this is a Grafana bug or sourced in the PRTG plugin.

Query > Metrics > Can Only Select *

I ran into this a few times, it seems the API refresh gets hung up (or caching interferes). Haven't noticed a pattern as to why or what gets done to cause it, yet.

Things to look for:

  • Date format of the user accesing PRTG's API from Grafana has to have their date format (in their PRTG profile) set to MM/DD/YYYY HH:MM:SS (AM/PM)
  • Make sure the correct group is being called (search the Group in PRTG and see if the device appears in the results, if it doesn't, move it to the group)
  • Log out of Grafana and log back in
  • After devices are moved to other groups, log out every time
  • CSP warnings in Firefox (portions of the javascript stopped loading as a result of this trigger, logging out and logging back in seemed to correct itself)

Also useful:

  • Sometimes it takes a while for the sensors to appear, simply tabbing or clicking to other fields can trigger the pull-downs to populate (I've found it takes a few seconds of doing this, sometimes - not sure if it is the trigger of the form updating, or simply entertainment while waiting for the dynamic refresh...)

  • Disable caching via the browser console:

    • Right-click on a blank part of the page > Inspect element > click the ... in the far right of the console window > Settings > check Disable HTTP Cache (when toolbox is open) and leave the console open while testing

  • Read the console messages in this same window (under the console tab)

v7.0.0+ - Plugin must be signed

A few people posted about this in the issues

From the release notes:

It’s possible to allow unsigned plugins using a configuration setting, but is something we strongly advise against doing.

Allowing unsigned plugins

Fix:

Windows:

  • Open C:\Program Files\GrafanaLabs\grafana\conf\custom.ini
  • Under [plugins] add allow_loading_unsigned_plugins = plugin1,plugin2
  • Mine looks like: 
    [plugins]
enable_alpha = false
app_tls_skip_verify_insecure = false
allow_loading_unsigned_plugins = yesoreyeram-boomtheme-panel,simpod-json-datasource,jasonlashua-prtg-datasource
  • Restart the Grafana service

Linux:

  • Open /etc/grafana/grafana.ini
  • Do the same for [plugins] as the Windows example above
  • service grafana-server restart

Forgot Password

Thank you to torkel for posting this tip!

On Linux:

sudo sqlite3 /var/lib/grafana/grafana.db
sqlite> update user set password = '59acf18b94d7eb0694c61e60ce44c110c7a683ac6a8f09580d626f90f4a242000746579358d77dd9e570e83fa24faa88a8a6', salt = 'F3FAxVm33R' where login = 'admin';
sqlite> .exit

This sets the "admin" username back to admin

Logs

On Linux installs, the Grafana logs are located at:

/var/log/grafana