save full output of check history

[P6g9YHK6]

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
2. Click on any point in history that has a long output
3. 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

[wh1te909]

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.

[P6g9YHK6]

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

[silversword411]

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

[P6g9YHK6]

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