monitor server load and cpu/ram/disk usage #1994

Closed
opened 2026-02-28 02:39:31 -05:00 by deekerman · 10 comments
Owner

Originally created by @tcpzix on GitHub (Mar 12, 2023).

⚠️ 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

it will be amazing if we can monitor server load and resource with kuma! :)

✔️ Solution

monitor disk cpu ram server load

Alternatives

No response

📝 Additional Context

No response

Originally created by @tcpzix on GitHub (Mar 12, 2023). ### ⚠️ 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 it will be amazing if we can monitor server load and resource with kuma! :) ### ✔️ Solution monitor disk cpu ram server load ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
deekerman 2026-02-28 02:39:31 -05:00
Author
Owner

@callamd commented on GitHub (Apr 7, 2023):

This would be great.

@callamd commented on GitHub (Apr 7, 2023): This would be great.
Author
Owner

@D3OXY commented on GitHub (Apr 11, 2023):

🔼

@D3OXY commented on GitHub (Apr 11, 2023): 🔼
Author
Owner

@Wizqdev commented on GitHub (May 7, 2023):

please do it requesting

@Wizqdev commented on GitHub (May 7, 2023): please do it requesting
Author
Owner

@kokofixcomputers commented on GitHub (May 7, 2023):

That would be great.

@kokofixcomputers commented on GitHub (May 7, 2023): That would be great.
Author
Owner

@jondycz commented on GitHub (May 10, 2023):

This is the only reason I haven't switched yet

@jondycz commented on GitHub (May 10, 2023): This is the only reason I haven't switched yet
Author
Owner

@kokofixcomputers commented on GitHub (May 23, 2023):

This is the only reason I haven't switched yet

What is the reason?

@kokofixcomputers commented on GitHub (May 23, 2023): > This is the only reason I haven't switched yet What is the reason?
Author
Owner

@CommanderStorm commented on GitHub (May 23, 2023):

@tcpzix
Is this a duplicate of #819?

@CommanderStorm commented on GitHub (May 23, 2023): @tcpzix Is this a duplicate of #819?
Author
Owner

@tcpzix commented on GitHub (May 29, 2023):

yes you right this is a duplicate of #819 and i'm sorry about that
thanks

On Wed, May 24, 2023 at 4:06 AM Frank Elsinga @.***>
wrote:

@tcpzix https://github.com/tcpzix
Is this a duplicate of #819
https://github.com/louislam/uptime-kuma/issues/819?


Reply to this email directly, view it on GitHub
https://github.com/louislam/uptime-kuma/issues/2921#issuecomment-1560296773,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKL2FTOYH4BYZ2HHHF3Q6TTXHVJ2VANCNFSM6AAAAAAVYAP7L4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@tcpzix commented on GitHub (May 29, 2023): yes you right this is a duplicate of #819 and i'm sorry about that thanks On Wed, May 24, 2023 at 4:06 AM Frank Elsinga ***@***.***> wrote: > @tcpzix <https://github.com/tcpzix> > Is this a duplicate of #819 > <https://github.com/louislam/uptime-kuma/issues/819>? > > — > Reply to this email directly, view it on GitHub > <https://github.com/louislam/uptime-kuma/issues/2921#issuecomment-1560296773>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AKL2FTOYH4BYZ2HHHF3Q6TTXHVJ2VANCNFSM6AAAAAAVYAP7L4> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@CommanderStorm commented on GitHub (May 29, 2023):

@tcpzix could you close this issue then? ^^

@CommanderStorm commented on GitHub (May 29, 2023): @tcpzix could you close this issue then? ^^
Author
Owner

@tcpzix commented on GitHub (May 29, 2023):

Yes, it's done.

On Mon, May 29, 2023 at 3:24 PM Frank Elsinga @.***>
wrote:

@tcpzix https://github.com/tcpzix could you close this issue then? ^^


Reply to this email directly, view it on GitHub
https://github.com/louislam/uptime-kuma/issues/2921#issuecomment-1567038100,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKL2FTNNACTFCUOZBEE5Q7TXISE5XANCNFSM6AAAAAAVYAP7L4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@tcpzix commented on GitHub (May 29, 2023): Yes, it's done. On Mon, May 29, 2023 at 3:24 PM Frank Elsinga ***@***.***> wrote: > @tcpzix <https://github.com/tcpzix> could you close this issue then? ^^ > > — > Reply to this email directly, view it on GitHub > <https://github.com/louislam/uptime-kuma/issues/2921#issuecomment-1567038100>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AKL2FTNNACTFCUOZBEE5Q7TXISE5XANCNFSM6AAAAAAVYAP7L4> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
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/uptime-kuma#1994
No description provided.