starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Is that possible to pass Zenduty tokens via Environment variables #3193

New issue

Closed

opened 2026-02-28 03:21:09 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-28 03:21:09 -05:00

Owner

Originally created by @Aj7Ay on GitHub (Mar 14, 2024).

⚠️ Please verify that this question has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

we are planning to use uptime kuma for our organisation

API is not supporting to create incidents (Will wait for 2.0 version)
Is that possible to pass the Zenduty token via Environment variables while building the project ?

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

💻 Operating System and Arch

Ubuntu 22.04

🌐 Browser

Google Chrome, Firefox

🖥️ Deployment Environment

Runtime:
Database:
Filesystem used to store the database on:
number of monitors:

Originally created by @Aj7Ay on GitHub (Mar 14, 2024). ### ⚠️ Please verify that this question has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem we are planning to use uptime kuma for our organisation 1. API is not supporting to create incidents (Will wait for 2.0 version) 2. Is that possible to pass the Zenduty token via Environment variables while building the project ? ### 📝 Error Message(s) or Log _No response_ ### 🐻 Uptime-Kuma Version 1 ### 💻 Operating System and Arch Ubuntu 22.04 ### 🌐 Browser Google Chrome, Firefox ### 🖥️ Deployment Environment - Runtime: - Database: - Filesystem used to store the database on: - number of monitors:

deekerman

2026-02-28 03:21:09 -05:00

closed this issue
added the
A:deployment

help
labels

deekerman commented

2026-02-28 03:21:16 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Mar 14, 2024):

API is not supporting to create incidents

Please see #118 for further details.
The work there is going on, but https://github.com/louislam/uptime-kuma/pull/3854 won't be done for the v2.0 release => was pushed one milestone further.
You can also use the third party python api wrapper to get this functionality sooner.

Is that possible to pass the Zenduty token via Environment

We currently also don't offer this notification provider.
For a guide how to contribute such a provider, please see https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md
All environment variables are listed here: https://github.com/louislam/uptime-kuma/wiki/Environment-Variables

while building the project

Build time (!= run time) would mean said token is baked into the docker image or the binary.
We don't allow for that for obvious security reasons ^^

@CommanderStorm commented on GitHub (Mar 14, 2024): > API is not supporting to create incidents Please see #118 for further details. The work there is going on, but https://github.com/louislam/uptime-kuma/pull/3854 won't be done for the v2.0 release => was pushed one milestone further. You can also use the [third party python api wrapper](https://uptime-kuma-api.readthedocs.io/en/latest/) to get this functionality sooner. > Is that possible to pass the Zenduty token via Environment We currently also don't offer this notification provider. For a guide how to contribute such a provider, please see https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md All environment variables are listed here: https://github.com/louislam/uptime-kuma/wiki/Environment-Variables > while building the project Build time (!= run time) would mean said token is baked into the docker image or the binary. We don't allow for that for obvious security reasons ^^

deekerman commented

2026-02-28 03:21:16 -05:00

Author

Owner

@Aj7Ay commented on GitHub (Mar 14, 2024):

I have another query
Is Twilio supporting voice call feature with uptime kuma so we can use it
Other than zenduty

On Thu, 14 Mar, 2024, 3:42 pm Frank Elsinga, @.***>
wrote:

API is not supporting to create incidents

Please see #118 https://github.com/louislam/uptime-kuma/issues/118 for
further details.
The work there is going on, but #3854
https://github.com/louislam/uptime-kuma/pull/3854 won't be done for the
v2.0 release => was pushed one milestone further.
You can also use the third party python api wrapper
https://uptime-kuma-api.readthedocs.io/en/latest/ to get this
functionality sooner.

Is that possible to pass the Zenduty token via Environment

We currently also don't offer this notification provider.
All environment variables are listed here:
https://github.com/louislam/uptime-kuma/wiki/Environment-Variables

while building the project

Build time (!= run time) would mean said token is baked into the docker
image or the binary.
We don't allow for that for obvious security reasons ^^

—
Reply to this email directly, view it on GitHub
https://github.com/louislam/uptime-kuma/issues/4579#issuecomment-1997092425,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2MXW445FGM5YQVQVHSKJT3YYFZX5AVCNFSM6AAAAABEVLWIKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJXGA4TENBSGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

@Aj7Ay commented on GitHub (Mar 14, 2024): I have another query Is Twilio supporting voice call feature with uptime kuma so we can use it Other than zenduty On Thu, 14 Mar, 2024, 3:42 pm Frank Elsinga, ***@***.***> wrote: > API is not supporting to create incidents > > Please see #118 <https://github.com/louislam/uptime-kuma/issues/118> for > further details. > The work there is going on, but #3854 > <https://github.com/louislam/uptime-kuma/pull/3854> won't be done for the > v2.0 release => was pushed one milestone further. > You can also use the third party python api wrapper > <https://uptime-kuma-api.readthedocs.io/en/latest/> to get this > functionality sooner. > > Is that possible to pass the Zenduty token via Environment > > We currently also don't offer this notification provider. > All environment variables are listed here: > https://github.com/louislam/uptime-kuma/wiki/Environment-Variables > > while building the project > > Build time (!= run time) would mean said token is baked into the docker > image or the binary. > We don't allow for that for obvious security reasons ^^ > > — > Reply to this email directly, view it on GitHub > <https://github.com/louislam/uptime-kuma/issues/4579#issuecomment-1997092425>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A2MXW445FGM5YQVQVHSKJT3YYFZX5AVCNFSM6AAAAABEVLWIKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJXGA4TENBSGU> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

deekerman commented

2026-02-28 03:21:16 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Mar 14, 2024):

No this is not implemented.
See https://github.com/louislam/uptime-kuma/issues/3295

@CommanderStorm commented on GitHub (Mar 14, 2024): No this is not implemented. See https://github.com/louislam/uptime-kuma/issues/3295

deekerman commented

2026-02-28 03:21:17 -05:00

Author

Owner

@Aj7Ay commented on GitHub (Mar 14, 2024):

We are trying to use Twilio sir
Right now we can integrate with Zenduty
When can we expect Twilio sir please

On Thu, 14 Mar, 2024, 5:30 pm Frank Elsinga, @.***>
wrote:

No this is not implemented.
See #3295 https://github.com/louislam/uptime-kuma/issues/3295

—
Reply to this email directly, view it on GitHub
https://github.com/louislam/uptime-kuma/issues/4579#issuecomment-1997284425,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2MXW43UQVXH4APINTPLYMLYYGGOTAVCNFSM6AAAAABEVLWIKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJXGI4DINBSGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

@Aj7Ay commented on GitHub (Mar 14, 2024): We are trying to use Twilio sir Right now we can integrate with Zenduty When can we expect Twilio sir please On Thu, 14 Mar, 2024, 5:30 pm Frank Elsinga, ***@***.***> wrote: > No this is not implemented. > See #3295 <https://github.com/louislam/uptime-kuma/issues/3295> > > — > Reply to this email directly, view it on GitHub > <https://github.com/louislam/uptime-kuma/issues/4579#issuecomment-1997284425>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A2MXW43UQVXH4APINTPLYMLYYGGOTAVCNFSM6AAAAABEVLWIKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJXGI4DINBSGU> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

deekerman commented

2026-02-28 03:21:17 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Mar 14, 2024):

When can we expect

This is open source.
This is not some faceless corporation with lots of stable engineering effort here.

work happens when it happens (or not) by people mostly in their spare time.
We don't offer timelines or deadlines or estimates except for the nearest of terms.
See #noestimates for further context why I don't think that that would add value.

Our contribution guidelines can be found here:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

@CommanderStorm commented on GitHub (Mar 14, 2024): > When can we expect This is open source. This is not some faceless corporation with lots of stable engineering effort here. - work happens when it happens (or not) by people mostly in their spare time. - We don't offer timelines or deadlines or estimates [except for the nearest of terms](https://github.com/louislam/uptime-kuma/milestones). See [#noestimates](https://www.youtube.com/watch?v=QVBlnCTu9Ms) for further context why I don't think that that would add value. Our contribution guidelines can be found here: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

deekerman commented

2026-02-28 03:21:17 -05:00

Author

Owner

@Aj7Ay commented on GitHub (Mar 14, 2024):

I understand sir
Thanks for the Information, and your Time

On Thu, 14 Mar, 2024, 5:41 pm Frank Elsinga, @.***>
wrote:

When can we expect

This is open source.
This is not some faceless corporation with lots of stable engineering
effort here.

work happens when it happens (or not) by people mostly in their
spare time.

We don't offer timelines or deadlines or estimates except for the
nearest of terms https://github.com/louislam/uptime-kuma/milestones.
See #noestimates https://www.youtube.com/watch?v=QVBlnCTu9Ms for
further context why I don't think that that would add value.

Our contribution guidelines can be found here:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

—
Reply to this email directly, view it on GitHub
https://github.com/louislam/uptime-kuma/issues/4579#issuecomment-1997302431,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2MXW42T47ZMTZSY72NFIE3YYGHWTAVCNFSM6AAAAABEVLWIKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJXGMYDENBTGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@Aj7Ay commented on GitHub (Mar 14, 2024): I understand sir Thanks for the Information, and your Time On Thu, 14 Mar, 2024, 5:41 pm Frank Elsinga, ***@***.***> wrote: > When can we expect > > This is open source. > This is not some faceless corporation with lots of stable engineering > effort here. > > - work happens when it happens (or not) by people mostly in their > spare time. > - We don't offer timelines or deadlines or estimates except for the > nearest of terms <https://github.com/louislam/uptime-kuma/milestones>. > See #noestimates <https://www.youtube.com/watch?v=QVBlnCTu9Ms> for > further context why I don't think that that would add value. > > Our contribution guidelines can be found here: > https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md > > — > Reply to this email directly, view it on GitHub > <https://github.com/louislam/uptime-kuma/issues/4579#issuecomment-1997302431>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A2MXW42T47ZMTZSY72NFIE3YYGHWTAVCNFSM6AAAAABEVLWIKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJXGMYDENBTGE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >