[GH-ISSUE #73] Healthcheck endpoint #47

New issue

Closed

opened 2026-03-15 12:17:02 +03:00 by kerem · 4 comments

kerem commented

2026-03-15 12:17:02 +03:00

Owner

Originally created by @IgnisDa on GitHub (Mar 25, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/73

Hello, awesome project! Could a healthcheck endpoint be added? Just an endpoint that can be used to check if the service is healthy. It is useful in docker-compose etc.

Originally created by @IgnisDa on GitHub (Mar 25, 2023). Original GitHub issue: https://github.com/axllent/mailpit/issues/73 Hello, awesome project! Could a healthcheck endpoint be added? Just an endpoint that can be used to check if the service is healthy. It is useful in docker-compose etc.

kerem closed this issue

2026-03-15 12:17:07 +03:00

kerem commented

2026-03-15 12:17:14 +03:00

Author

Owner

@axllent commented on GitHub (Mar 25, 2023):

Hi @IgnisDa . There are actually already two kubernetes-specific handlers which should both work for what you want, namely http://localhost:8025/livez or http://localhost:8025/readyz. I was considering adding this to the Dockerfile, however it would only work if using the default 8025 port and HTTP - if the user specifies another port or TLS via either an environment variable or command-line option it would fail, so I haven't implemented this.

Does this help?

@axllent commented on GitHub (Mar 25, 2023): Hi @IgnisDa . There are actually already two kubernetes-specific handlers which should both work for what you want, namely `http://localhost:8025/livez` or `http://localhost:8025/readyz`. I was considering adding this to the Dockerfile, however it would only work if using the default 8025 port and HTTP - if the user specifies another port or TLS via either an environment variable or command-line option it would fail, so I haven't implemented this. Does this help?

kerem commented

2026-03-15 12:17:19 +03:00

Author

Owner

@IgnisDa commented on GitHub (Mar 25, 2023):

Yep it does work. Would be worth documenting them on https://github.com/axllent/mailpit/tree/develop/docs/apiv1.

@IgnisDa commented on GitHub (Mar 25, 2023): Yep it does work. Would be worth documenting them on https://github.com/axllent/mailpit/tree/develop/docs/apiv1.

kerem commented

2026-03-15 12:17:24 +03:00

Author

Owner

@axllent commented on GitHub (Mar 25, 2023):

Thanks for the feedback. Actually any of those API calls should technically work too. Given that this isn't necessarily an API-related feature but more of a system-related feature, I have now documented them on the website 👍

@axllent commented on GitHub (Mar 25, 2023): Thanks for the feedback. Actually any of those API calls should technically work too. Given that this isn't necessarily an API-related feature but more of a system-related feature, I have now documented them on the [website](https://mailpit.axllent.org/docs/integration/healthcheck/) :+1:

kerem commented

2026-03-15 12:17:29 +03:00

Author

Owner

@99linesofcode commented on GitHub (Jan 8, 2024):

Perhaps it would be more obvious to others but I quickly checked here to determine that the endpoint is exposed on the dashboard and not on the mailpit service itself. Might be worth mentioning in the documentation.

@99linesofcode commented on GitHub (Jan 8, 2024): Perhaps it would be more obvious to others but I quickly checked here to determine that the endpoint is exposed on the dashboard and not on the mailpit service itself. Might be worth mentioning in the documentation.

kerem referenced this issue

2026-03-15 14:18:00 +03:00

[PR #47] [CLOSED] Bump axios from 1.2.6 to 1.3.4 #420