dundee / disk_usage_exporter Goto Github PK

View Code? Open in Web Editor NEW

75.0 75.0 12.0 156 KB

Disk Usage Prometheus Exporter

License: MIT License

Makefile 18.73% Go 81.27%

disk_usage_exporter's People

Stargazers

Watchers

Forkers

neredera isgasho tangyiyong pathcl bearboy80 phpfs jahnavin-amd golang108 liunan-ms lukegoooo rsudre

disk_usage_exporter's Issues

duplicate dir if path endswith /

disk_usage_exporter -p=/data: node_disk_usage_bytes{path="/data/xxxx"} 8192

disk_usage_exporter -p=/data/: node_disk_usage_bytes{path="/data/data/xxxx"} 8192

Incorrect release binary architecture

disk_usage_exporter_linux_amd64: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>

Follow Sym-Links

Hi
we have some directories that have sym-links in but the exporter see these are empty folders and does not calculate the size , Is there way to treat the links as real folders?

Thanks
Adam

Wrong values for disk usage on windows

I've compiled your exporter on windows with go build and it compiled without any error.
Also it's possible to execute the resulting binary disk_usage_exporter.exe.

E:\disk_usage_exporter-0.4.0>disk_usage_exporter.exe -m file -p z:\
time="2023-09-13T10:48:10+02:00" level=info msg="Disk Usage Prometheus Exporter <<< filled in by build >>>\tbuild date: <<< filled in by build >>>\tsha1: <<< filled in by build >>>\tGo: go1.21.1\tGOOS: windows\tGOARCH: amd64"
time="2023-09-13T10:48:18+02:00" level=info msg="Analysis done"
time="2023-09-13T10:48:19+02:00" level=info msg="Stored stats in file ./disk-usage-exporter.prom"
time="2023-09-13T10:48:19+02:00" level=info msg="Done - exiting."

However, the directory and file sizes in the output do not match the real sizes in the file system.

# TYPE node_disk_usage_level_1_bytes gauge
node_disk_usage_level_1_bytes{path="e:\\Install"} 12288
node_disk_usage_level_1_bytes{path="e:\\temp"} 1.3725696e+07

[Question] Basic Auth

Hello there, I am new to prometheus and I just take a look at prometheus guides basic auth.

I tried the same in disk usage exporter config, more or less like this:

basic_auth_users:
  admin: <password-hash>
analyzed-path: /var/www/media
dir-level: 1

but I still can access the endpoint without username and password.

I already restart the systemd service but there's no change.

So I want to make sure, is disk usage exporter support basic auth?
If it is, then how can we implement basic auth with disk usage exporter?
Thank you!

Having issue while using in multi POD

Hello,

I am using 3 pods and disk_usage_exporter as sidecar. But out of 3 only one pod running without any issue and scraping the metrics even with less resources. But other two pods behaving weird, not scraping the metrics, if I try to scrape the metrics locally, pods are getting restarted with OOM issue. I have allocated enough resources still the same.

[root@local-path-provisioner-monitoring-wwp9n /]# curl http://localhost:9995/metrics curl: (52) Empty reply from server

And the other one immediate response

`[root@local-path-provisioner-monitoring-plq4d /]# curl http://localhost:9995/metrics

HELP go_gc_duration_seconds A summary of the pause duration of garbage collection cycles.

TYPE go_gc_duration_seconds summary

go_gc_duration_seconds{quantile="0"} 6.5438e-05
go_gc_duration_seconds{quantile="0.25"} 8.8972e-05`

And other two

Definitely it's not for scrape timeout as it's failing locally .

Could you please help me out to fix this issue.

It cannot be run on CentOS.

package name：disk_usage_exporter_linux_amd64.tgz

 [root@localhost opt]# tar -zxvf disk_usage_exporter_linux_amd64.tgz -C diskusage/
._disk_usage_exporter_linux_amd64
tar: Ignoring unknown extended header keyword `LIBARCHIVE.xattr.com.apple.provenance'
disk_usage_exporter_linux_amd64

`[root@localhost diskusage]# file disk_usage_exporter_linux_amd64

disk_usage_exporter_linux_amd64: Mach-O 64-bit executable
`

How can I run it on CentOS? Please advise.

Multi "analyzed-path" with customatisable "dir-level"

Hi @dundee !
I suggest you an improvement in order to monitor different repository with customisable "dir-level".
The goal of the suggestion is to evaluate several targeted repository while consuming the least system resources as possible.
Regards,
Bruno

Metrics of non-existent folders

Hello.
I faced the following issue and hope you'll be able to give some advice about it.
I use disk_usage_exporter to monitor disk usage of databases inside mysql instance. Recently I noticed that exporter shows old data.

Disk_usage_exporter runs as additional container of mysql pod:

  disk-exporter:
    Image:         ghcr.io/dundee/disk_usage_exporter/disk_usage_exporter-c4084307c537335c2ddb6f4b9b527422:latest
    Image ID:      docker-pullable://ghcr.io/dundee/disk_usage_exporter/disk_usage_exporter-c4084307c537335c2ddb6f4b9b527422@sha256:320b9e61b93ce4d339de9b9462fbcad862710f8a6884bd62ba631a9055eecb27
    Port:          9995/TCP
    Host Port:     0/TCP
    Args:
      -l=1
      -p=/var/lib/mysql
    State:          Running
      Started:      Sat, 31 Dec 2022 13:30:50 +0200
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     200m
      memory:  384Mi
    Requests:
      cpu:        100m
      memory:     256Mi
    Environment:  <none>
    Mounts:
      /var/lib/mysql from data (rw)

There are folders that are not present in pod itself as they were removed long time ago, for example:

sh-4.2$ ls -lah /var/lib/mysql/old_database
ls: cannot access /var/lib/mysql/old_database: No such file or directory
sh-4.2$ ls -lah /var/lib/mysql/xtrabackup_logfile
ls: cannot access /var/lib/mysql/xtrabackup_logfile: No such file or directory

However I still can see those folders metrics in browser at http://127.0.0.1:8080/metrics:

node_disk_usage_bytes{path="/var/lib/mysql/old_database"} 1.3676023808e+10
node_disk_usage_bytes{path="/var/lib/mysql/xtrabackup_logfile"} 7.314219008e+09

And in general from endpoint I get much more metrics than currently existing folders/files. Disk_usage_exporter returns not only current folders/files, but also all folders/files that ever existed at monitored path.
My expectation was that disk_usage_exporter provides data only for existing folders/files.

Is the output with all ever existed data is expected? If there any cache within disk_usage_exporter that holds old data can it be cleared?

Grafana dashboard example ?

Do you have a grafana dashboard file example to understand what we need to do to show metrics ?

I seen the link you shared but I'm not sure about what I need to do to create dashboard for metric available with disk_usage_exporter.

Docker support

Hello,
Is it possible to package this exporter as a docker image? I have Grafana, Prometheus and various other exporters running as docker containers. believe many others are doing the same.

As I'm still learning Linux, I can't even begin to understand how to install this standalone.