-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add setting for metrics endpoint #328
Comments
I think we can remove current Another separate endpoint with metrics that cannot be generated by parsing the logs such as the number of accounts in |
New doveauth-based counter after merging #349 looks like this in
|
Current mtail scripts:
|
not sure i fully understand but can you do a PR to produce mtail data? Does nine have a wireguard setup and if so, where is it documented? |
It's all documented in the server readme, both wireguard and mtail setup. But wireguard is not related to chatmail, how metrics are collected is up to the server admin. |
Closed with #388, there is now We should also do something about |
Currently metrics are exposed over https under
/metrics
, but without any authentication. Metrics are generated with a cronjob. Current approach to metric generation is very limited, we have #183 open for exposing disk space and #273 (comment)Since we want more dynamic metrics and expose data such as disk space that should not be publicly available, we will need to expose them over TCP and only to secure network, e.g. wireguard one.
By default we can expose metrics to
localhost:9123
or something like this. Someone who wants to monitor chatmail instance can then create a VPN (e.g. wireguard) interface and point the metrics server there to be collected with prometheus on the other side.The text was updated successfully, but these errors were encountered: