[GH-ISSUE #995] Scripts run thru bulk script doesn't appear in audit log #606

Closed
opened 2026-03-02 02:17:37 +03:00 by kerem · 2 comments
Owner

Originally created by @silversword411 on GitHub (Feb 27, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/995

Originally assigned to: @sadnub on GitHub.

Run script against individual agents.
Check Audit log, doesn't reflect anything. Check History, you see the script run.

Originally created by @silversword411 on GitHub (Feb 27, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/995 Originally assigned to: @sadnub on GitHub. Run script against individual agents. Check Audit log, doesn't reflect anything. Check History, you see the script run.
kerem 2026-03-02 02:17:37 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@sadnub commented on GitHub (Mar 17, 2022):

When bulk actions are run, it will show in the audit log as a Bulk Action versus under the individual agents.

<!-- gh-comment-id:1069773351 --> @sadnub commented on GitHub (Mar 17, 2022): When bulk actions are run, it will show in the audit log as a Bulk Action versus under the individual agents.
Author
Owner

@silversword411 commented on GitHub (Mar 17, 2022):

When bulk actions are run, it will show in the audit log as a Bulk Action versus under the individual agents.

This is how it's always worked?

Intuitively I'm expecting if something happens on the agent, it'll be in the agent history. Can we have it also show up there, not just in the server-wide audit log?

<!-- gh-comment-id:1070910711 --> @silversword411 commented on GitHub (Mar 17, 2022): > When bulk actions are run, it will show in the audit log as a Bulk Action versus under the individual agents. This is how it's always worked? Intuitively I'm expecting if something happens on the agent, it'll be in the agent history. Can we have it also show up there, not just in the server-wide audit log?
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/tacticalrmm#606
No description provided.