starred/uptime-kuma

Fork 0

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

Version monitoring - monitor if updates are avalibale for services #536

New issue

Open

opened 2026-02-28 01:49:47 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-28 01:49:47 -05:00

Owner

Originally created by @ccoenen on GitHub (Nov 8, 2021).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

I am hosting a few services myself, and the majority of these are "off the shelf" things like nextcloud, mattermost or WordPress.

I would love if uptime kuma could
a) identify the installed version
and
b) check against a canonical source for updates
then
c) notifying you, in case you're falling behind with updates

✔️ Solution

uptime-kuma would provide a way to easily add software packages to it. Each software package would consist of

name
canonical "this version is latest" url/api (for example: github releases page of the project)
a way to identify the installed version (for example: HTTP-Header, HTML-Meta-Tag Generator, embedded as info in the site's footer, or wherever a software offers that information)

❓ Alternatives

Hand-Checking for Updates or subscribing to mailinglists, release notes and other things for all the software you deploy.

📝 Additional Context

No response

Originally created by @ccoenen on GitHub (Nov 8, 2021). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Monitor ### 🔖 Feature description I am hosting a few services myself, and the majority of these are "off the shelf" things like nextcloud, mattermost or WordPress. I would love if uptime kuma could a) identify the installed version and b) check against a canonical source for updates then c) notifying you, in case you're falling behind with updates ### ✔️ Solution uptime-kuma would provide a way to easily add software packages to it. Each software package would consist of - name - canonical "this version is latest" url/api (for example: github releases page of the project) - a way to identify the installed version (for example: HTTP-Header, HTML-Meta-Tag Generator, embedded as info in the site's footer, or wherever a software offers that information) ### ❓ Alternatives Hand-Checking for Updates or subscribing to mailinglists, release notes and other things for all the software you deploy. ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:monitor

labels

2026-02-28 01:49:47 -05:00

deekerman commented

2026-02-28 01:49:51 -05:00

Author

Owner

@ccoenen commented on GitHub (Nov 8, 2021):

Candidates:

nextcloud:
a server will report its version at <hostname>/status.php

{
  "installed":true,
  "maintenance":false,
  "needsDbUpgrade":false,
  "version":"22.2.0.2",
  "versionstring":"22.2.0",
  "edition":"",
  "productname":"Nextcloud",
  "extendedSupport":false
}

Current version could be obtained from https://nextcloud.com/changelog/

WordPress
an installation will usually have the version as part of the cache-busting in any pages' script-tag (better source probably needed)
current version can be obtained here: https://wordpress.org/download/releases/
HedgeDoc
the overwiew page has a link to the source code that's used, including git hash

current version can be obtained from https://github.com/hedgedoc/hedgedoc/releases

@ccoenen commented on GitHub (Nov 8, 2021): Candidates: - **nextcloud:** a server will report its version at `<hostname>/status.php` ```json { "installed":true, "maintenance":false, "needsDbUpgrade":false, "version":"22.2.0.2", "versionstring":"22.2.0", "edition":"", "productname":"Nextcloud", "extendedSupport":false } ``` Current version could be obtained from https://nextcloud.com/changelog/ - **WordPress** an installation will usually have the version as part of the cache-busting in any pages' script-tag (better source probably needed) current version can be obtained here: https://wordpress.org/download/releases/ - **HedgeDoc** the overwiew page has a link to the source code that's used, including git hash ![grafik](https://user-images.githubusercontent.com/124909/140729477-eff478f7-13c3-423e-af5b-1e0f2b6fe0ae.png) current version can be obtained from https://github.com/hedgedoc/hedgedoc/releases

deekerman commented

2026-02-28 01:49:53 -05:00

Author

Owner

@deefdragon commented on GitHub (Nov 8, 2021):

I do believe this is inline with what UK is for given the cert monitors, and I think this is JUST inside of feasible with an extension to the current http monitor, but I feel it would require jumping through some hoops to where I am not sure if it is worth it at this time.

@deefdragon commented on GitHub (Nov 8, 2021): I do believe this is inline with what UK is for given the cert monitors, and I think this is JUST inside of feasible with an extension to the current http monitor, but I feel it would require jumping through some hoops to where I am not sure if it is worth it at this time.

deekerman commented

2026-02-28 01:49:53 -05:00

Author

Owner

@chakflying commented on GitHub (Nov 9, 2021):

I think it would make more sense if we have a plugin interface for these things, then the user can optionally enable it and reduce UI clutter. The EditMonitor screen is a lot more complicated than it was already.

@chakflying commented on GitHub (Nov 9, 2021): I think it would make more sense if we have a plugin interface for these things, then the user can optionally enable it and reduce UI clutter. The EditMonitor screen is a lot more complicated than it was already.

deekerman commented

2026-02-28 01:49:53 -05:00

Author

Owner

@ccoenen commented on GitHub (Nov 9, 2021):

I would be perfectly happy with a plugin system! In that case we could perhaps collect more examples here to make sure a plugin system's specification can support a good variety?

@ccoenen commented on GitHub (Nov 9, 2021): I would be perfectly happy with a plugin system! In that case we could perhaps collect more examples here to make sure a plugin system's specification can support a good variety?

deekerman commented

2026-02-28 01:49:53 -05:00

Author

Owner

@ccoenen commented on GitHub (Nov 9, 2021):

Other interesting candidates:

GitLab, Gitea
minio
Matomo (Piwik)
BBB, JitsiMeet
FreeScout Helpdesk
Lemmy
Grocy
Jellyfin
Mastodon, Pleorama, Diaspora*, Pixelfed, Friendica
Peertube, OSP, Owncast

@ccoenen commented on GitHub (Nov 9, 2021): Other interesting candidates: * GitLab, Gitea * minio * Matomo (Piwik) * BBB, JitsiMeet * FreeScout Helpdesk * Lemmy * Grocy * Jellyfin * Mastodon, Pleorama, Diaspora*, Pixelfed, Friendica * Peertube, OSP, Owncast

deekerman commented

2026-02-28 01:49:53 -05:00

Author

Owner

@deefdragon commented on GitHub (Nov 9, 2021):

Cross referencing: plugins is currently grouped in #117

Custom monitors are indeed one of the best examples of where plugins would be usefull. This issue and #805 (along with the ones that @ccoenen brought up) would likely best be implemented via custom plugins.

@deefdragon commented on GitHub (Nov 9, 2021): Cross referencing: plugins is currently grouped in #117 Custom monitors are indeed one of the best examples of where plugins would be usefull. This issue and #805 (along with the ones that @ccoenen brought up) would likely best be implemented via custom plugins.

deekerman commented

2026-02-28 01:49:53 -05:00

Author

Owner

@ccoenen commented on GitHub (Nov 9, 2021):

For these checks, I'd find it useful if they were tied to an existing monitor, somehow. In a way that's similar to the existing certificate checks.

I monitor git.example.com anyway for uptime. But if I could somehow give it the "Gitlab" trait, then I would have this information in one place. Also, the update check would not have to happen every minute. It would probably suffice to have that daily.

@ccoenen commented on GitHub (Nov 9, 2021): For these checks, I'd find it useful if they were tied to an existing monitor, somehow. In a way that's similar to the existing certificate checks. I monitor `git.example.com` anyway for uptime. But if I could somehow give it the "Gitlab" trait, then I would have this information in one place. Also, the update check would not have to happen every minute. It would probably suffice to have that daily.

deekerman commented

2026-02-28 01:49:53 -05:00

Author

Owner

@dmnktoe commented on GitHub (Mar 15, 2023):

For these checks, I'd find it useful if they were tied to an existing monitor, somehow. In a way that's similar to the existing certificate checks.

I monitor git.example.com anyway for uptime. But if I could somehow give it the "Gitlab" trait, then I would have this information in one place. Also, the update check would not have to happen every minute. It would probably suffice to have that daily.

Oh yes, that would be insanely useful. I haven't seen any other tool which can lookup up new software updates on different servers. This can cause so many headaches handling not up-to-date software on various servers.

Edit: Even Uptime Kuma could be a plugin candidate. More plugin suggestions: Sentry, LibreTime, Sourcegraph and Rocket.Chat.

@dmnktoe commented on GitHub (Mar 15, 2023): > For these checks, I'd find it useful if they were tied to an existing monitor, somehow. In a way that's similar to the existing certificate checks. > > I monitor `git.example.com` anyway for uptime. But if I could somehow give it the "Gitlab" trait, then I would have this information in one place. Also, the update check would not have to happen every minute. It would probably suffice to have that daily. Oh yes, that would be insanely useful. I haven't seen any other tool which can lookup up new software updates on different servers. This can cause so many headaches handling not up-to-date software on various servers. Edit: Even Uptime Kuma could be a plugin candidate. More plugin suggestions: `Sentry`, `LibreTime`, `Sourcegraph` and `Rocket.Chat`.