search

smilebasti / npmGrafStats

This project exports NginxProxyManager Logs to InfluxDB for displaying them in a Grafana Dashboard.
GNU General Public License v3.0
149 stars 10 forks source link

no data in influxdb 2 #4

Closed GieGit closed 1 year ago

GieGit commented 1 year ago

i have installed the tool. unfortunately no data is written to the bucket. i can't find any error message in the logs either

smilebasti commented 1 year ago

Hi, thanks for the hint to add some debug logs.

Until i add them have you checked if you set the Organization, Bucket, Host and Token correctly?

GieGit commented 1 year ago

Hi yes I have checked all the data again and they are all correctly in the stack. I have also created a new API Token which only has rights to the bucket.

smilebasti commented 1 year ago

Ok i have tried to reproduce the error but wasn't able to. I pulled the latest docker-images of nginx-reverse-proxy-manager, npmgrafstats, influxdb and even grafana. I tried entering wrong credentials for influx in the npmgrafstats config, but that has thrown me an error-message. I tested the api token with only write access for npmgrafstats-bucket and it worked.

Can you explain a little bit more? Which version of influxdb and npm are you running? Is influxdb on same host and in Docker?Has influxdb any error/access logs? Did you recreate the npmgrafstats container after changing the config?

GieGit commented 1 year ago

Hi thanks for your responce. i have the following versions influxdb : v2.6.1 npm: v2.10.2 Is influxdb on the same host and in Docker: No, influxdb is installed on its own server. Did you recreate the npmgrafstats container after changing the configuration? Yes I deleted the images and pulled it again from the docker hub

smilebasti commented 1 year ago

I am running the same setup but tried to recreate everything. It worked for.

If you see this in your logs it should work because no connection error occurs and the data is send. image

I think it has to do with your Influxdb but i don't know. I'm closing this issue but if you have any further information you can reopen it.