-
Notifications
You must be signed in to change notification settings - Fork 68
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
Nginx with fping_mtr & std_fping #147
Comments
data is mapped to graphs according to probe and group names, maybe there is some overlap there? we dont have a mtr+fping example, but there have been configs posted in #136 that implement both, albeit in a standalone setup, while it sounds like you are going for a distributed one, but maybe there is some help to be gleaned from there. For nginx doing a reverse proxy may be an ok solution for a simple set up. (i have not personally tested) |
Thank you kindly for your reply. I don't claim to be familiar with the subject, but I was trying to heed the "WARNING: This is a development server. Do not use it in a production deployment." I can get it working fine if I'm just running vodka. Do people typically run this under vodka? As it iterates, it hits this: vaping.plugins.fping_mtr queue emission to zmq_vodka (0) __init__.py:231 2021-11-17 13:15:27,158 - vaping.daemon - ERROR: Address already in use vaping.daemon Address already in use daemon.py:214 So, I tried to map mtr to another address: - name: zmq_vodka2 type: zeromq bind: tcp://127.0.0.1:6022 That ran, but then the graph went wonky. |
If I could get a glance at the config for this site, that would be swell, thkx. (I see the nginx part is already posted) https://vaping.20c.com/ |
Apologies, this time I'm just looking for help.
I'm looking for hints on how to get these to work together. I tried to get them to work by setting different bind addrs, but they both got mapped to the same graph and it looked very wrong. Examples or hints appreciated, thanks. (Leaving off messed up config for brevity)
The text was updated successfully, but these errors were encountered: