[Plugin] Prometheus unRAID Plugins

[simo241]

yes , and Host access to custom networks is enabled in Settings/docker

[ich777]

1 minute ago, simo241 said:

yes , and Host access to custom networks is enabled in Settings/docker

Can you try to open up a console from the AdGuard container and see if you can actually ping Unraid?

[simo241]

I discover that console of adguard is not working when i open is automatically close

[simo241]

But i can ping Ad guard from unraid

[ich777]

7 minutes ago, simo241 said:

I discover that console of adguard is not working when i open is automatically close

But AdGuard is working I think?

 

7 minutes ago, simo241 said:

But i can ping Ad guard from unraid

You can also try to open up a Unraid console and enter:

docker exec -ti CONTAINERNAME /bin/bash

(replace CONTAINERNAME with your container name <- case sensitive and maybe change /bin/bash to /bin/sh depending on the shell that is running in the container)

 

This is basically the same as when you open up a Console window from the container.

[simo241]

hi, thank you for your help, with your help i been able to ping unraid from adguard

I confirm adguard is working but not the console

[ich777]

7 minutes ago, simo241 said:

hi, thank you for your help, with your help i been able to ping unraid from adguard

I confirm adguard is working but not the console

It seems then something else is wrong on your setup, I've now tried it again on my test system with a clean install from AdGuard, Prometheus, Grafana and the plugin and it works without a issue.

[simo241]

in grafana i am able to get all the info from unraid with node exporter , in prometheus is running after few second  i get this

 

[shiz]

Open up the file /boot/config/plugins/prometheus_firtzbox_exporter/settings.cfg and edit the line where it says "fritz_additional=" so that it looks like:

fritz_additional=-gateway-url http://YOURIP:49000 -gateway-luaurl http://YOURIP

 
Of course insert the IP of your Fritzbox where it says YOURIP and stop the exporter first before doing this.

unfortunately it does not work for me. I followed your instructions for setting up the fritz box with a new user. is there a log I can check? when I start the plug in the status stays 'stopped'. thanks for your help

Gesendet von meinem SM-N986B mit Tapatalk

[sonic6]

19 hours ago, shiz said:

unfortunately it does not work for me. I followed your instructions for setting up the fritz box with a new user. is there a log I can check? when I start the plug in the status stays 'stopped'. thanks for your help

You can try this: 

 

and doublecheck username/password and user permissions:

even that upnp is activated

[ich777]

On 5/5/2022 at 2:05 PM, shiz said:

thanks for your help

Please change the command like @sonic6 mentioned, then it should work just fine.

[shiz]

Please change the command like @sonic6 mentioned, then it should work just fine.

@sonic6 @ich777 thanks, it is working now.

Gesendet von meinem SM-N986B mit Tapatalk

[Robert Sitavu]

Hi Everyone,

 

I installed prometheus successfully however the container won't start.

I am using Unraid version: 6.10.1

Guide Used: Unraid | Unraid Data Monitoring with Prometheus and Grafana

Error Logs:

ts=2022-05-23T08:43:54.878Z caller=main.go:488 level=info msg="No time or size retention was set so using the default time retention" duration=15d
ts=2022-05-23T08:43:54.878Z caller=main.go:525 level=info msg="Starting Prometheus" version="(version=2.35.0, branch=HEAD, revision=6656cd29fe6ac92bab91ecec0fe162ef0f187654)"
ts=2022-05-23T08:43:54.878Z caller=main.go:530 level=info build_context="(go=go1.18.1, user=root@cf6852b14d68, date=20220421-09:53:42)"
ts=2022-05-23T08:43:54.878Z caller=main.go:531 level=info host_details="(Linux 5.15.40-Unraid #1 SMP Mon May 16 10:05:44 PDT 2022 x86_64 3dec108b666f (none))"
ts=2022-05-23T08:43:54.878Z caller=main.go:532 level=info fd_limits="(soft=40960, hard=40960)"
ts=2022-05-23T08:43:54.878Z caller=main.go:533 level=info vm_limits="(soft=unlimited, hard=unlimited)"
ts=2022-05-23T08:43:54.878Z caller=query_logger.go:90 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied"
panic: Unable to create mmap-ed active query log

goroutine 1 [running]:
github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffd01d38e9d, 0xb}, 0x14, {0x3757500, 0xc00059b8b0})
        /app/promql/query_logger.go:120 +0x3d5
main.main()
        /app/cmd/prometheus/main.go:587 +0x61bf
ts=2022-05-23T08:44:03.171Z caller=main.go:488 level=info msg="No time or size retention was set so using the default time retention" duration=15d
ts=2022-05-23T08:44:03.171Z caller=main.go:525 level=info msg="Starting Prometheus" version="(version=2.35.0, branch=HEAD, revision=6656cd29fe6ac92bab91ecec0fe162ef0f187654)"
ts=2022-05-23T08:44:03.171Z caller=main.go:530 level=info build_context="(go=go1.18.1, user=root@cf6852b14d68, date=20220421-09:53:42)"
ts=2022-05-23T08:44:03.171Z caller=main.go:531 level=info host_details="(Linux 5.15.40-Unraid #1 SMP Mon May 16 10:05:44 PDT 2022 x86_64 3dec108b666f (none))"
ts=2022-05-23T08:44:03.171Z caller=main.go:532 level=info fd_limits="(soft=40960, hard=40960)"
ts=2022-05-23T08:44:03.171Z caller=main.go:533 level=info vm_limits="(soft=unlimited, hard=unlimited)"
ts=2022-05-23T08:44:03.171Z caller=query_logger.go:90 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied"
panic: Unable to create mmap-ed active query log

goroutine 1 [running]:
github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffdc3a94e9d, 0xb}, 0x14, {0x3757500, 0xc00074f6d0})
        /app/promql/query_logger.go:120 +0x3d5
main.main()
        /app/cmd/prometheus/main.go:587 +0x61bf
ts=2022-05-23T08:50:35.294Z caller=main.go:488 level=info msg="No time or size retention was set so using the default time retention" duration=15d
ts=2022-05-23T08:50:35.294Z caller=main.go:525 level=info msg="Starting Prometheus" version="(version=2.35.0, branch=HEAD, revision=6656cd29fe6ac92bab91ecec0fe162ef0f187654)"
ts=2022-05-23T08:50:35.294Z caller=main.go:530 level=info build_context="(go=go1.18.1, user=root@cf6852b14d68, date=20220421-09:53:42)"
ts=2022-05-23T08:50:35.294Z caller=main.go:531 level=info host_details="(Linux 5.15.40-Unraid #1 SMP Mon May 16 10:05:44 PDT 2022 x86_64 3dec108b666f (none))"
ts=2022-05-23T08:50:35.294Z caller=main.go:532 level=info fd_limits="(soft=40960, hard=40960)"
ts=2022-05-23T08:50:35.294Z caller=main.go:533 level=info vm_limits="(soft=unlimited, hard=unlimited)"
ts=2022-05-23T08:50:35.295Z caller=query_logger.go:90 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied"
panic: Unable to create mmap-ed active query log

goroutine 1 [running]:
github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffd1f0ede9d, 0xb}, 0x14, {0x3757500, 0xc000827090})
        /app/promql/query_logger.go:120 +0x3d5
main.main()
        /app/cmd/prometheus/main.go:587 +0x61bf
ts=2022-05-23T08:59:55.398Z caller=main.go:488 level=info msg="No time or size retention was set so using the default time retention" duration=15d
ts=2022-05-23T08:59:55.399Z caller=main.go:525 level=info msg="Starting Prometheus" version="(version=2.35.0, branch=HEAD, revision=6656cd29fe6ac92bab91ecec0fe162ef0f187654)"
ts=2022-05-23T08:59:55.399Z caller=main.go:530 level=info build_context="(go=go1.18.1, user=root@cf6852b14d68, date=20220421-09:53:42)"
ts=2022-05-23T08:59:55.399Z caller=main.go:531 level=info host_details="(Linux 5.15.40-Unraid #1 SMP Mon May 16 10:05:44 PDT 2022 x86_64 3dec108b666f (none))"
ts=2022-05-23T08:59:55.399Z caller=main.go:532 level=info fd_limits="(soft=40960, hard=40960)"
ts=2022-05-23T08:59:55.399Z caller=main.go:533 level=info vm_limits="(soft=unlimited, hard=unlimited)"
ts=2022-05-23T08:59:55.399Z caller=query_logger.go:90 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied"
panic: Unable to create mmap-ed active query log

goroutine 1 [running]:
github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffd5b979e9d, 0xb}, 0x14, {0x3757500, 0xc0009879a0})
        /app/promql/query_logger.go:120 +0x3d5
main.main()
        /app/cmd/prometheus/main.go:587 +0x61bf

** Press ANY KEY to close this window ** 

 

[ich777]

5 minutes ago, Robert Sitavu said:

I installed prometheus successfully however the container won't start.

Please post this in the Prometheus Support Thread here, I've only written the Guide on how to install it in conjunction with my plugins and I'm not the maintainer from the Prometheus container.

[Robert Sitavu]

1 hour ago, ich777 said:

Please post this in the Prometheus Support Thread here, I've only written the Guide on how to install it in conjunction with my plugins and I'm not the maintainer from the Prometheus container.

I will do thank you 

 

[flow]

On 7/3/2021 at 4:25 PM, ich777 said:

Prometheus PiHole Exporter

 

Note: You can connect to any PiHole on your local network and of course if you run it on unRAID in a Docker container or VM.
 

1. Download and install the Prometheus PiHole Exporter plugin from the CA App:
   
    
2. Go to the plugin settings by clicking on "Settings -> Pi-Hole Exporter (at the bottom of the Settings page)":
   
    
3. Enter your IP from PiHole and also your API Token and click on "Confirm & Start":
   
   (Please note that if you run your PiHole in a Docker container in a Custom network like br0 you have to enable the option "Enable host access" in your Docker settings, otherwise the plugin can't connect to your PiHole instance)
   
   To get your API Token go to your PiHole instance, Login and click on "Settings -> API / Web interface -> Show API Token -> Yes, show API Token":
   
   
    
4. After that you should see in the right top corner that the Exporter is running and details about it:
   
    
5. Open up the prometheus.yml (Step 4 + 5 from the first post), add a line with '- targets: ["YOURSERVERIP:9617"]' (please change "YOURSERVERIP" to your Server IP), save and close the file:
   
    
6. Go to the Docker page and restart Prometheus:
   
    
7. Open up the Grafana WebUI:
   
    

8. In Grafana click on "+ -> Import":
   
    

9. Now we are going to import a preconfigured Dashboard for the PiHole Exporter from Grafana.com (Source), to do this simply enter the ID (10176) from the Dasboard and click "Load":
   
    

10. In the next screen rename the Dashboard to your liking and click on "Import"
     

11. Now you should be greeted with something like this (please keep in mind that the Dashboard can display N/A at some values since there is not enough data available, wait a few minutes and you will see that the values are filled in):
    
    (Now you will notice that this warning: "Panel plugin not found: grafana-piechar-panel" appears on the Dasboard, to fix this follow the next steps)
     

12. Go to your Docker page and click on Grafana and select "Console":
    
     

13. In the next window enter the following 'grafana-cli plugins install grafana-piechart-panel' and press RETURN:
    
     

14. After that close the Console window and restart the Grafana Docker container:
    
     

15. Now go back to your PiHole Dashboard within Grafana and you should now see that the Dasboard is fully loaded:
    

 

 

 

ATTENTION

Please note if you restart your PiHole container the Exporter will stop and you have to manually start it from the plugin configuration page with the "START" button.

 

This is also applies if you have CA Backup installed and the container is beeing backed up.

 

To workaround that you don't have to manually restart it after each CA Backup do the following steps:

 

1. Go to Settings and click on the bottom on "Backup/Restore Appdata":
   
    
2. Confirm the Warning that pops up and scroll all the way down to the bottom and click on "Show Advanced Settings":
   
    
3. At Pi-Hole make sure that you click on the switch so that it shows "Don't Stop":
   
    
4. Scroll down to the bottom and click "Apply":
   

 

 

NO DATA SHOWING UP IN THE PIHOLE DASHBOARD

If no data is showing up in the PiHole Dashboard it is most likely the case that you have configured another Datasource like Telegraf in Grafana, to solve this issue go to this post:

 

Hi, I can’t find the checkbox for enable host access.

Where do I find it?

At the moment I can’t access Pi-hole via the exporter.

 

Best regards,

Florian

[sonic6]

22 minutes ago, flow said:

Hi, I can’t find the checkbox for enable host access.

Where do I find it?

[flow]

3 hours ago, sonic6 said:

Found it, needed to activate advanced view. Thank you.

[Masterwishx]

What is the right way to add --storage.tsdb.retention.time=365d to prometheus.yml ?

also wanted to ask Grafana is not saving the values only shows what its getting ?

[ich777]

10 minutes ago, Masterwishx said:

What is the right way to add --storage.tsdb.retention.time=365d to prometheus.yml ?

also wanted to ask Grafana is not saving the values only shows what its getting ?

This is a question for the Prometheus or better speaking Grafana Support Thread.

[Masterwishx]

2 hours ago, ich777 said:

This is a question for the Prometheus

OK Thanks

[Bitbass]

On 2/28/2022 at 6:41 PM, Bitbass said:

I'm an old crusty IT guy and it doesn't make any sense to me either. This is the error I get from the Docker on the primary Unraid:

 

If I telnet to the primary Unraid and "curl http://172.16.172.30:9100/metrics" it just hangs indefinitely. If I "curl http://172.16.172.30:9100" I get an immediate response of the top level page with a link to the metrics page in the middle.

 

If I go to http://172.16.172.30:9100/metrics from my Mac mini, which is on the same network as the primary Unraid, I can browse to that, I can curl it, everything works.

 

If I telnet to the target Unraid and "curl http://172.16.172.30:9100/metrics" I get an immediate response. Not going to localhost, but the NIC's IP from itself. 

 

So, it's like something on the Primary Unraid, at the system level, is unhappy with the html response from the /metrics page on the target.

Upgraded to 6.10.3 on both systems and still having the problem. The primary is on a different subnet from the target, but the firewall that's in the middle isn't causing a problem for anything else. I can access the target metrics page from other systems next to the primary, and the primary can access an Ubuntu target at 172.16.172.31, right next to the Unraid target. When I curl from the primary Unraid cli to the target Unraid metrics page it just hangs indefinitely. 

 

Is it possible something related to DNS is getting stuck? I have different "names" on each Unraid system, but the primary is simply called "unraid". I can't really change that. Is it possible the target is somehow responding with "unraid" to the query and the primary is getting confused and looking at itself? Maybe the target is trying to resolve "unraid" and getting confused. Could that be happening with the exporter plugin?

 

Not sure that's what's going on. Here's the output from the curl:

 

root@unraid:~# curl -v http://172.16.172.30:9100/metrics
*   Trying 172.16.172.30:9100...
* Connected to 172.16.172.30 (172.16.172.30) port 9100 (#0)
> GET /metrics HTTP/1.1
> Host: 172.16.172.30:9100
> User-Agent: curl/7.83.1
> Accept: */*
> 
************hangs at this point and I quit out of it
^C
root@unraid:~# curl -v http://172.16.172.31:9100/metrics
*   Trying 172.16.172.31:9100...
* Connected to 172.16.172.31 (172.16.172.31) port 9100 (#0)
> GET /metrics HTTP/1.1
> Host: 172.16.172.31:9100
> User-Agent: curl/7.83.1
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: text/plain; version=0.0.4; charset=utf-8
< Date: Mon, 20 Jun 2022 16:38:29 GMT
< Transfer-Encoding: chunked
< 
*********** full normal scrape after this. I've truncated it.

 

Edited June 20, 2022 by Bitbass

[Bitbass]

From the target, pinging "unraid" does not resolve. Unless there's something hard coded into the node exporter plugin related to "unraid", I'm at a loss.

[ich777]

1 minute ago, Bitbass said:

From the target, pinging "unraid" does not resolve. Unless there's something hard coded into the node exporter plugin related to "unraid", I'm at a loss.

Try to restart the Docker service once or do a server reboot and see if it fixes the issue.

[Bitbass]

I've rebooted as part of the 6.10.3 upgrades on both sides, but I just restarted the Prometheus container on the primary and same result.