Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install on top of existing Prometheus and grafana docker? #306

Open
everything13 opened this issue Jan 9, 2022 · 9 comments
Open

Install on top of existing Prometheus and grafana docker? #306

everything13 opened this issue Jan 9, 2022 · 9 comments
Labels

Comments

@everything13
Copy link

I already have Pi-Hole, Prometheus and grafana Dockers running on my Pi as I have a dashboard setup for monitoring the rpi. Is there any way I can set up the internet pi as a separate dashboard within my existing grafana and Prometheus dockers?

@martinbrose
Copy link
Contributor

martinbrose commented Mar 3, 2022

Yes, I had the same problem. I think you have a conflict for port 9090 (for prometheus).

I changed the internet-pi's use of 9090 to 9080.
For this, I had to perform two changes:

.internet-monitoring/docker-compose.yml
Change prometheus port setting from
ports: - 9090:9090
to
ports: - 9080:9090
This tells docker-compose to expose the containers internal port 9090 to external 9080.

./templates/prometheus.yml.j2
- targets: ['localhost:9090']
to
- targets: ['localhost:9080']

You will need to do something similar for grafana too, if your existing docker container uses port 3030 already.
But I think it might be only in ./internet-monitoring/docker-compose.yml
Change the port 3030 to a port of your choosing:
- 3030:3000

@stale
Copy link

stale bot commented Jun 12, 2022

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@stale stale bot added the stale label Jun 12, 2022
@johntdavis84
Copy link

Does this solution result in two Prometheus/Grafana containers running side by side (one standalone, and one part of the Internet Pi)?

I actually came here looking to see if there's a way to incorporate Internet Pi into an existing Grafana/Prometheus service so I just have a single login to see all my dashboards in a single place.

@stale
Copy link

stale bot commented Jun 26, 2022

This issue is no longer marked for closure.

@stale stale bot removed the stale label Jun 26, 2022
@martinbrose
Copy link
Contributor

martinbrose commented Jun 27, 2022

Pretty sure it would result in two Prometheus/Grafana containers running side by side.

If you want to add the internet monitoring to your existing Grafan/Prometheus, you would need to get creative and remove the Grafana/Prometheus tasks from the ansible internet-monitoring task (folder tasks).
And then add the required configs from the folder templates, internet-monitoring/prometheus, and internet-monitoring/grafana into your existing installs.
Plus, you would need to remove prometheus and grafana sections from the docker-compose.yml. And somehow you need to make sure that your existing Prometheus can reach the internet-pi docker containers.
So quite a bit of complexity... but not unsolvable.

@johntdavis84
Copy link

johntdavis84 commented Jun 27, 2022 via email

@stale
Copy link

stale bot commented Oct 15, 2022

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@stale stale bot added the stale label Oct 15, 2022
@stale
Copy link

stale bot commented Dec 24, 2022

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.

@github-actions github-actions bot removed the stale label Sep 18, 2023
Copy link

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@github-actions github-actions bot added the stale label Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants