mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 16:56:00 +03:00
[GH-ISSUE #497] feature: Metrics endpoint #322
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#322
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 @avesst on GitHub (May 19, 2025).
Original GitHub issue: https://github.com/axllent/mailpit/issues/497
Hi,
It would be cool if Mailpit would expose a
/metricsPrometheus endpoint that could be scraped and sent to Prometheus for keeping track of the Mailpit usage, like connections, mails received etc.@axllent commented on GitHub (May 20, 2025):
Hi. There is already a
/api/v1/infoendpoint which is documented here. Is this not what you're after, and if not, then what specifically do you need?@avesst commented on GitHub (May 20, 2025):
Ah I see. Well, we are using VictoriaMetrics to store timeseries metrics about our servers and services. This is usually done by scraping an HTTP endpoint for Prometheus compatible data structure.
To be clear, this is a nice to have, not a need to have, maybe I can work with the API endpint. :)
@github-actions[bot] commented on GitHub (May 28, 2025):
This issue has been marked as stale because it has been open for 7 days with no activity.
@axllent commented on GitHub (Jun 6, 2025):
I have just released v1.26.0 which contains @Tigger2014's PR. I'll close this now, but feel free to reopen if you have any issues, or notice the metrics aren't being recorded as intended. One day I'll experiment with Prometheus, but not yet ... ;-) Thanks again!
@avesst commented on GitHub (Jun 6, 2025):
Wow! Thanks, that was quick :)
@axllent commented on GitHub (Jun 6, 2025):
It's all thanks to @Tigger2014, who not only provided the code ,but also the website documentation (a fair bit of work) 🥇