mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #13] Bandwidth Usage #13
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#13
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 @NoName805 on GitHub (Sep 4, 2018).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/13
Can you add the bandwidth usage log with graph for this project?
@jc21 commented on GitHub (Sep 4, 2018):
It's possibly in the distant future but I think something like this is better accomplished with an Elasticsearch / logstash setup.
@L3tum commented on GitHub (Jan 23, 2019):
I know this is an older issue, but as far as I can see every access is written into stdout so datadog or companions should be able to pick it up
@the1ts commented on GitHub (Oct 25, 2021):
This looks to me like a job for another tool, there are plenty of very old tools that analyse web logs and give this type of information and modern tools that do it well for container type environments.
Making NPM do everything will only make it harder to get devs to work on it as complexity accelerates.
@github-actions[bot] commented on GitHub (Apr 4, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (May 13, 2025):
Issue was closed due to inactivity.