mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #985] Visualizing connections origin and influxdb integration #827
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#827
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @maxdd on GitHub (Mar 31, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/985
Hi,
i have seen plenty of repos that help figure out and plot the origin/source of the connections
https://github.com/Festeazy/nginxproxymanagerGraf
https://github.com/ma-karai/nginxproxymanagerGraf
https://github.com/ratibor78/geostat (maybe too much)
I honestly feel like it is a pity to have a docker running just because of a python script that tries to send data to influxdb.
Do you think it will be possible to add the following feature such that one can enable it via env variable?
Ideally influxdb2 should be the go to version.
Regards,
@github-actions[bot] commented on GitHub (Mar 15, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 26, 2025):
Issue was closed due to inactivity.