[GH-ISSUE #1998] [Feature request] add RAM consumption in the Summary #1251

New issue

Open

opened 2026-03-02 02:22:08 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 02:22:08 +03:00

Owner

Originally created by @P6g9YHK6 on GitHub (Sep 9, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1998

Is your feature request related to a problem? Please describe.
it is currently impossible to know how much ram is used outide of checks results

Describe the solution you'd like
just like Disks spaces add visual feedback on how much ram is currently used on the device.

Describe alternatives you've considered
none

Additional context

Originally created by @P6g9YHK6 on GitHub (Sep 9, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1998 **Is your feature request related to a problem? Please describe.** it is currently impossible to know how much ram is used outide of checks results **Describe the solution you'd like** just like Disks spaces add visual feedback on how much ram is currently used on the device. **Describe alternatives you've considered** none **Additional context** ![image](https://github.com/user-attachments/assets/cd84ff85-4178-4e95-8007-2800aebaf403) ![image](https://github.com/user-attachments/assets/6fe0cc62-4402-4efd-a60b-7e8180eabf50)

kerem commented

2026-03-02 02:22:10 +03:00

Author

Owner

@isv-one commented on GitHub (Sep 25, 2024):

RAM consumption is very dynamic and can change as quickly as second to second. This is not a practical suggestion. You should configure a Memory usage check in your automation policies that alerts based on a provided threshold. This also has the added benefit of retaining the check history as a graph that you can view as 24-hour, 7 day, 30 day, or All Time.

@isv-one commented on GitHub (Sep 25, 2024): RAM consumption is very dynamic and can change as quickly as second to second. This is not a practical suggestion. You should configure a Memory usage check in your automation policies that alerts based on a provided threshold. This also has the added benefit of retaining the check history as a graph that you can view as 24-hour, 7 day, 30 day, or All Time.

kerem commented

2026-03-02 02:22:10 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Sep 25, 2024):

RAM consumption is very dynamic and can change as quickly as second to second. This is not a practical suggestion. You should configure a Memory usage check in your automation policies that alerts based on a provided threshold. This also has the added benefit of retaining the check history as a graph that you can view as 24-hour, 7 day, 30 day, or All Time.

maybe true for workstations but not so much for servers where a simple preview can give a good idea of the level of activity on the services but i am pretty sure it could be applied to other use-cases

@P6g9YHK6 commented on GitHub (Sep 25, 2024): > RAM consumption is very dynamic and can change as quickly as second to second. This is not a practical suggestion. You should configure a Memory usage check in your automation policies that alerts based on a provided threshold. This also has the added benefit of retaining the check history as a graph that you can view as 24-hour, 7 day, 30 day, or All Time. maybe true for workstations but not so much for servers where a simple preview can give a good idea of the level of activity on the services but i am pretty sure it could be applied to other use-cases