Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upQuestion : Setting up Prometheus (dockerized) to monitor OpenVPN clients #1978
Comments
grobie
added
kind/question
component/config
labels
Sep 15, 2016
This comment has been minimized.
This comment has been minimized.
|
Are you wondering how best to discover the service, route traffic to it, or perhaps how you might get metrics from it @grobie? |
This comment has been minimized.
This comment has been minimized.
|
Please send questions to the prometheus-users usergroup https://groups.google.com/forum/#!forum/prometheus-users instead. |
grobie
closed this
Mar 5, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ddewaele commentedSep 12, 2016
What did you do?
Setup prometheus / alertmanager in their docker containers on a user defined bridged network.
Works fine to monitor assets that are running on the hosts / reachable via the internet.
I'm hoping for some guidance on how such a setup could work to monitor OpenVPN clients connected via a tun+ interface (either directly on the host, or via another docker container on the same network).
The idea is to monitor external devices (that expose prometheus metrics) that connect to the OpenVPN.
I've asked a more generic question (not involving Prometheus, as I assume this has nothing to do with Prometheus itself) on superuser.
If somebody has some pointers on how to get this up and running I'd be happy to write up a blog post on how such a setup could work.