[GH-ISSUE #799] Please consider adding Telegram as a notification service #561

Closed
opened 2026-02-25 23:42:52 +03:00 by kerem · 7 comments
Owner

Originally created by @tessierp on GitHub (Mar 2, 2023).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/799

This is a feature request and would like to ask you to consider adding Telegram support as a notification service.

Originally created by @tessierp on GitHub (Mar 2, 2023). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/799 This is a feature request and would like to ask you to consider adding Telegram support as a notification service.
kerem closed this issue 2026-02-25 23:42:52 +03:00
Author
Owner

@cuu508 commented on GitHub (Mar 6, 2023):

Telegram is already supported, see–

<!-- gh-comment-id:1455497254 --> @cuu508 commented on GitHub (Mar 6, 2023): Telegram is already supported, see– * https://healthchecks.io/integrations/telegram/ * https://github.com/healthchecks/healthchecks#telegram
Author
Owner

@Polve commented on GitHub (Jun 24, 2024):

Is it available to use it on personal custom install?

<!-- gh-comment-id:2186555912 --> @Polve commented on GitHub (Jun 24, 2024): Is it available to use it on personal custom install?
Author
Owner

@tessierp commented on GitHub (Jun 24, 2024):

Telegram is already supported, see–

Thanks for sharing. However, what I meant was to add support directly in the UI. I'm using a docker container, linuxserver/healthchecks, which doesn't seem to have support to configure Telegram from the compose file. I could very well login to the container and activate telegram but it would be gone the next time the container restarts.

Out of the box, this is the only list available to me

image

<!-- gh-comment-id:2186774029 --> @tessierp commented on GitHub (Jun 24, 2024): > Telegram is already supported, see– > > * https://healthchecks.io/integrations/telegram/ > * https://github.com/healthchecks/healthchecks#telegram Thanks for sharing. However, what I meant was to add support directly in the UI. I'm using a docker container, linuxserver/healthchecks, which doesn't seem to have support to configure Telegram from the compose file. I could very well login to the container and activate telegram but it would be gone the next time the container restarts. Out of the box, this is the only list available to me ![image](https://github.com/healthchecks/healthchecks/assets/6784384/e047e113-4b66-4b3e-baed-8984512131c8)
Author
Owner

@Polve commented on GitHub (Jun 24, 2024):

My bad, I didn't read carefully enough the configuration!
Thanks!

<!-- gh-comment-id:2186796386 --> @Polve commented on GitHub (Jun 24, 2024): My bad, I didn't read carefully enough the configuration! Thanks!
Author
Owner

@cuu508 commented on GitHub (Jun 26, 2024):

I'm using a docker container, linuxserver/healthchecks, which doesn't seem to have support to configure Telegram from the compose file.

Did you mean to file this issue in linuxserver/docker-healthchecks but filed here by error?

<!-- gh-comment-id:2191037284 --> @cuu508 commented on GitHub (Jun 26, 2024): > I'm using a docker container, linuxserver/healthchecks, which doesn't seem to have support to configure Telegram from the compose file. Did you mean to file this issue in [linuxserver/docker-healthchecks](https://github.com/linuxserver/docker-healthchecks) but filed here by error?
Author
Owner

@tessierp commented on GitHub (Jun 26, 2024):

I'm using a docker container, linuxserver/healthchecks, which doesn't seem to have support to configure Telegram from the compose file.

Did you mean to file this issue in linuxserver/docker-healthchecks but filed here by error?

I meant this one https://hub.docker.com/r/linuxserver/healthchecks but we are talking about the same thing. linuxserver/healthchecks is the name of the image.

<!-- gh-comment-id:2191484709 --> @tessierp commented on GitHub (Jun 26, 2024): > > I'm using a docker container, linuxserver/healthchecks, which doesn't seem to have support to configure Telegram from the compose file. > > Did you mean to file this issue in [linuxserver/docker-healthchecks](https://github.com/linuxserver/docker-healthchecks) but filed here by error? I meant this one https://hub.docker.com/r/linuxserver/healthchecks but we are talking about the same thing. linuxserver/healthchecks is the name of the image.
Author
Owner

@cuu508 commented on GitHub (Jun 26, 2024):

@tessierp I do not maintain the linuxserver image, it is a separate project. To fix issues with it, or receive support regarding it, you will need to work with the LinuxServer team.

<!-- gh-comment-id:2192223889 --> @cuu508 commented on GitHub (Jun 26, 2024): @tessierp I do not maintain the linuxserver image, it is a separate project. To fix issues with it, or receive support regarding it, you will need to work with the LinuxServer team.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/healthchecks#561
No description provided.