You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then I edited my docker compose file and commented out the original image and put the tag in. I then docker down and docker up’d the compose file to get everything up and running.
This took care of the issues I had graylog. However there ended up being more.
2- influxDB. The original compose file calls for 1.8.4-alpine. Latest didn’t work for me as cerebro only wants a 1.X version. influxdb:1.5.1 worked for me… or at least enough for me to continue through the instructions in cerebro, which takes me to part 3.
3- cerebro. The listed ‘image: lmenezes/cerebro’ didn’t build for me. I had to clone and build a repo separately. GitHub - lmenezes/cerebro-docker: official cerebro docker image . Make sure to tag it similar to the instructions above for mongo. Repeat same steps in compose file but cerebro section and you should have no problem deploying with compose up.
Final thoughts:
I was able to get it all to work–ish. I am having issues with grafana right now. The DPI tab is working (except the geolocation data/map for some reason) but I cant get the firewall dashboard to work. I dont know how to troubleshoot this or fix it and Im at another–possibly immovable-- dead end. I dont know if its influxdb, if its grafana, or what. I am way outside my comfort zone. I hope this information helps someone. Always grateful to find resources that get me past whatever problems I have with my own projects.
For the love of all that is holy, if someone can help get this working I'd be grateful. I'd be even more grateful if someone would make a public fork and get everything up to date and working and publish an update showing everything working.
The text was updated successfully, but these errors were encountered:
Instaled today (Jan 2024) firewall logs are working on my vm but with grafana 7.4.0. Only change i made that is not covered by the instructions provided here is the adjustment of the timestamp in Graylog(see Pipelines on https://github.com/devopstales/pfsense-graylog)
I looked at the pull requests and went to the most recent that I could see, thenaturalwill's repo.
I got this deployed to an rPi4-8gb running piOS 64bit. MongoDB wouldn't deploy so i had to clone and build locally GitHub - themattman/mongodb-raspberrypi-docker: Docker Images for MongoDB on Raspberry Pi.
Then I edited my docker compose file and commented out the original image and put the tag in. I then docker down and docker up’d the compose file to get everything up and running.
This took care of the issues I had graylog. However there ended up being more.
2- influxDB. The original compose file calls for 1.8.4-alpine. Latest didn’t work for me as cerebro only wants a 1.X version. influxdb:1.5.1 worked for me… or at least enough for me to continue through the instructions in cerebro, which takes me to part 3.
3- cerebro. The listed ‘image: lmenezes/cerebro’ didn’t build for me. I had to clone and build a repo separately. GitHub - lmenezes/cerebro-docker: official cerebro docker image . Make sure to tag it similar to the instructions above for mongo. Repeat same steps in compose file but cerebro section and you should have no problem deploying with compose up.
Final thoughts:
I was able to get it all to work–ish. I am having issues with grafana right now. The DPI tab is working (except the geolocation data/map for some reason) but I cant get the firewall dashboard to work. I dont know how to troubleshoot this or fix it and Im at another–possibly immovable-- dead end. I dont know if its influxdb, if its grafana, or what. I am way outside my comfort zone. I hope this information helps someone. Always grateful to find resources that get me past whatever problems I have with my own projects.
For the love of all that is holy, if someone can help get this working I'd be grateful. I'd be even more grateful if someone would make a public fork and get everything up to date and working and publish an update showing everything working.
The text was updated successfully, but these errors were encountered: