starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 06:55:52 +03:00

[GH-ISSUE #1933] save full output of check history #3150

New issue

Open

opened 2026-03-14 06:42:58 +03:00 by kerem · 4 comments

kerem commented

2026-03-14 06:42:58 +03:00

Owner

Originally created by @P6g9YHK6 on GitHub (Jul 25, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1933

Server Info (please complete the following information):

OS: Debian 12
Browser: Edge
RMM Version (as shown in top left of web UI): 0.19.2

Installation Method:

Standard
Standard with --insecure flag at install
Docker

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI):2.7.0
Agent OS: any

Describe the bug
The STDOUT and STDERR is not visible if more than a couple of charr long in the history nor a full output can be found in the CSV export

To Reproduce
Steps to reproduce the behavior:

Go to check history
Click on any point in history that has a long output
See error

Expected behavior
either allow to copy the output on click or make it show the whole thing on click
and additionally add the STDOUT STDERR to the CSV export

Screenshots

Additional context
https://discord.com/channels/736478043522072608/889513877124042762/1265966553816367168

Originally created by @P6g9YHK6 on GitHub (Jul 25, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1933 **Server Info (please complete the following information):** - OS: Debian 12 - Browser: Edge - RMM Version (as shown in top left of web UI): 0.19.2 **Installation Method:** - [X] Standard - [ ] Standard with `--insecure` flag at install - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI):2.7.0 - Agent OS: any **Describe the bug** The STDOUT and STDERR is not visible if more than a couple of charr long in the history nor a full output can be found in the CSV export **To Reproduce** Steps to reproduce the behavior: 1. Go to check history 3. Click on any point in history that has a long output 5. See error **Expected behavior** either allow to copy the output on click or make it show the whole thing on click and additionally add the STDOUT STDERR to the CSV export **Screenshots** ![image](https://github.com/user-attachments/assets/09177c4b-51e7-4b0c-8497-171a3a32da17) **Additional context** https://discord.com/channels/736478043522072608/889513877124042762/1265966553816367168

kerem added the

enhancement

label

2026-03-14 06:42:58 +03:00

kerem commented

2026-03-14 06:43:09 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jul 25, 2024):

removed bug label and added enhancement as technically this is by design, we are intentionally truncating the output before it's saved in the database.

@wh1te909 commented on GitHub (Jul 25, 2024): removed bug label and added enhancement as technically this is by design, we are intentionally truncating the output before it's saved in the database.

kerem commented

2026-03-14 06:43:14 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Oct 31, 2024):

if the data start's being too bulky it should maybe be saved into another DB because i am not sure postgress would survive all the checks in full :D

@P6g9YHK6 commented on GitHub (Oct 31, 2024): if the data start's being too bulky it should maybe be saved into another DB because i am not sure postgress would survive all the checks in full :D

kerem commented

2026-03-14 06:43:19 +03:00

Author

Owner

@silversword411 commented on GitHub (Nov 1, 2024):

How many characters is it currently saving? Maybe an increase to a reasonable 256-512 would be a good quick fix.

@silversword411 commented on GitHub (Nov 1, 2024): How many characters is it currently saving? Maybe an increase to a reasonable 256-512 would be a good quick fix.

kerem commented

2026-03-14 06:43:24 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Nov 1, 2024):

How many characters is it currently saving? Maybe an increase to a reasonable 256-512 would be a good quick fix.

this and on top fixing the csv export feature would indeed be a good patchwork
https://github.com/amidaware/tacticalrmm/issues/2025

@P6g9YHK6 commented on GitHub (Nov 1, 2024): > How many characters is it currently saving? Maybe an increase to a reasonable 256-512 would be a good quick fix. this and on top fixing the csv export feature would indeed be a good patchwork https://github.com/amidaware/tacticalrmm/issues/2025