-
-
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
Setup mtail #388
Setup mtail #388
Conversation
85666fa
to
205732e
Compare
but this makes it hard to merge right away, no? also, there is an "mtail" debian package which is probably better to use than downloading from google server and unpacking etc. |
98d0b77
to
f5166bb
Compare
5054e61
to
7fac976
Compare
7fac976
to
23994ea
Compare
CHANGELOG.md
Outdated
If you want to collect the metrics with Prometheus, | ||
setup a private network (e.g. WireGuard interface) | ||
and assign an IP address from this network to the host. | ||
If unsure, set this setting to `127.0.0.1`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is it a required setting? It should be fine to leave it empty, and then no mtail is setup or run?
This runs
mtail
at localhost, so you can queryhttp://127.0.0.1:3903/metrics
and get metrics collected by parsing the log files to get some counters of the number of sent/received mails.This can then be plugged into Prometheus. Setting up Prometheus is outside of the scope of cmdeploy.
What is missing is a setting in the .ini file to set the host and port. Listening on 127.0.0.1 is not very useful, normally you would have a wireguard network for metric collection and make mtail listen on the IP address from this network.
Another problem currently is that deployment fails while trying to copy
mtail
binary if it is already running. We should stopmtail
service before replacing the binary somehow.