starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-30 08:55:55 +03:00

[GH-ISSUE #2095] [Feature Request] Advanced Detailed Logging and Features to accommodate #3249

New issue

Open

opened 2026-03-14 06:57:58 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @NavCC on GitHub (Dec 6, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2095

Feature Request: Advanced Detailed Logging

Description:
Requesting an option for [Advanced Detailed Logging] to enhance the system's logging capabilities for device connectivity and remote session events. This feature would provide deeper insights and traceability, particularly for actions that are currently logged only when specific alerts are enabled.

Key Features:

Device Connectivity Logging:
    Log [disconnection] and [re-connection] events for all devices, regardless of whether alerts for these events are enabled.
    Include timestamps and device identifiers to accurately track offline and online durations.

Remote Session Logging:
    Disconnection Events: Log when a [remote session ends], capturing details about the session duration.
    Session Type: Log the type of remote session:
        [Take Control]
        [Remote Background]

    Idle Timeout Auto-Disconnect:
        Introduce an optional feature to automatically terminate remote sessions after a specified period of inactivity (e.g., 15, 30, or 60 minutes).
        
Enhanced Details:
    Provide a clear distinction between user-initiated disconnections and system-triggered (e.g., auto-disconnect) disconnections.
    Include IP addresses or user identifiers (if available) associated with the session for audit purposes.

Optional Settings for Advanced Logging:
    Allow administrators to toggle Advanced Detailed Logging on or off per site, client, or globally.
    Include filters to specify which event types are logged (e.g., device disconnections, session auto-disconnects, or specific session types).

Benefits:

Enhanced Auditability:
    Provides comprehensive logs for compliance and troubleshooting.
    Tracks exact periods of device downtime and remote session usage.

Improved Security:
    Automatically terminate idle sessions to reduce unauthorized access risks.
    Maintain detailed logs for session activity for forensic purposes.

Operational Efficiency:
    Enables better monitoring of device and session uptime/downtime.
    Offers clear insights into inactive session trends to optimize resource usage.

This feature would significantly enhance the system's logging capabilities, making it a more powerful tool for administrators and auditors. Please consider this addition to improve traceability and operational oversight.

Originally created by @NavCC on GitHub (Dec 6, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2095 Feature Request: Advanced Detailed Logging Description: Requesting an option for [Advanced Detailed Logging] to enhance the system's logging capabilities for device connectivity and remote session events. This feature would provide deeper insights and traceability, particularly for actions that are currently logged only when specific alerts are enabled. Key Features: Device Connectivity Logging: Log [disconnection] and [re-connection] events for all devices, regardless of whether alerts for these events are enabled. Include timestamps and device identifiers to accurately track offline and online durations. Remote Session Logging: Disconnection Events: Log when a [remote session ends], capturing details about the session duration. Session Type: Log the type of remote session: [Take Control] [Remote Background] Idle Timeout Auto-Disconnect: Introduce an optional feature to automatically terminate remote sessions after a specified period of inactivity (e.g., 15, 30, or 60 minutes). Enhanced Details: Provide a clear distinction between user-initiated disconnections and system-triggered (e.g., auto-disconnect) disconnections. Include IP addresses or user identifiers (if available) associated with the session for audit purposes. Optional Settings for Advanced Logging: Allow administrators to toggle Advanced Detailed Logging on or off per site, client, or globally. Include filters to specify which event types are logged (e.g., device disconnections, session auto-disconnects, or specific session types). Benefits: Enhanced Auditability: Provides comprehensive logs for compliance and troubleshooting. Tracks exact periods of device downtime and remote session usage. Improved Security: Automatically terminate idle sessions to reduce unauthorized access risks. Maintain detailed logs for session activity for forensic purposes. Operational Efficiency: Enables better monitoring of device and session uptime/downtime. Offers clear insights into inactive session trends to optimize resource usage. This feature would significantly enhance the system's logging capabilities, making it a more powerful tool for administrators and auditors. Please consider this addition to improve traceability and operational oversight.

kerem commented

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

Author

Owner

@P6g9YHK6 commented on GitHub (Dec 6, 2024):

i love this chatgpt non sense issue :)

anyway all the points are either already there in the audit tab or not a trmm thing

except "Device Connectivity Logging" where it would be nice to see a graph/log of all the connections events to the rmm by the agent

"Remote Session Logging:" already in place
"Idle Timeout Auto-Disconnect:" it's a mesh central thing
"Enhanced Details:" already in place would need more details if anything is missing

"Optional Settings for Advanced Logging:" you can customise the audit report already.

@P6g9YHK6 commented on GitHub (Dec 6, 2024): i love this chatgpt non sense issue :) anyway all the points are either already there in the audit tab or not a trmm thing except "Device Connectivity Logging" where it would be nice to see a graph/log of all the connections events to the rmm by the agent "Remote Session Logging:" already in place "Idle Timeout Auto-Disconnect:" it's a mesh central thing "Enhanced Details:" already in place would need more details if anything is missing "Optional Settings for Advanced Logging:" you can customise the audit report already.

kerem commented

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

Author

Owner

@NavCC commented on GitHub (Dec 6, 2024):

GPT well, lol :)

"Remote Session Logging:" already in place - both [take control] and [remote background] - [connect] and [disconnect]?
"Idle Timeout Auto-Disconnect:" it's a mesh central thing - i'll dive in..
"Enhanced Details:" already in place would need more details if anything is missing

"Optional Settings for Advanced Logging:" you can customise the audit report already. - Can you point me in a direction / url? This might negate the need for anything else.

@NavCC commented on GitHub (Dec 6, 2024): GPT well, lol :) "Remote Session Logging:" already in place - both [take control] and [remote background] - [connect] and [disconnect]? "Idle Timeout Auto-Disconnect:" it's a mesh central thing - i'll dive in.. "Enhanced Details:" already in place would need more details if anything is missing "Optional Settings for Advanced Logging:" you can customise the audit report already. - Can you point me in a direction / url? This might negate the need for anything else.

kerem commented

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

Author

Owner

@P6g9YHK6 commented on GitHub (Dec 6, 2024):

there is no the disconnect logs

some stuff is missing but they are aware of it
https://github.com/amidaware/tacticalrmm/issues/2080#issuecomment-2498880975

don't hesitate to say what you think is missing in a more constructive way rather than a chat gpt generated issue 👯

@P6g9YHK6 commented on GitHub (Dec 6, 2024): there is no the disconnect logs ![image](https://github.com/user-attachments/assets/cb8b7891-a6ff-4e69-8f5a-f489a3bf2b0f) some stuff is missing but they are aware of it https://github.com/amidaware/tacticalrmm/issues/2080#issuecomment-2498880975 don't hesitate to say what you think is missing in a more constructive way rather than a chat gpt generated issue 👯

kerem commented

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

Author

Owner

@NavCC commented on GitHub (Dec 8, 2024):

Oh, well that is what i was asking for in the feature request. [Type of connection (Take control or Remote Background)] and [Disconnect of session - which could be created when the remote window is closed manually or automatically with idle timeouts], which apparently are in Mesh so i need to find that. Additionally, was after disconnect and reconnect audits so i can report overall uptime per agent. I've turned on Alerts for this but don't really need alerts, just audits.

@NavCC commented on GitHub (Dec 8, 2024): Oh, well that is what i was asking for in the feature request. [Type of connection (Take control or Remote Background)] and [Disconnect of session - which could be created when the remote window is closed manually or automatically with idle timeouts], which apparently are in Mesh so i need to find that. Additionally, was after disconnect and reconnect audits so i can report overall uptime per agent. I've turned on Alerts for this but don't really need alerts, just audits.

kerem commented

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

Author

Owner

@BuddiesD commented on GitHub (Jan 31, 2025):

Logging the Disconnects of Remote Sessions (Take control or Remote Background) would be good.

@BuddiesD commented on GitHub (Jan 31, 2025): Logging the Disconnects of Remote Sessions (Take control or Remote Background) would be good.

kerem commented

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

Author

Owner

@silversword411 commented on GitHub (Feb 18, 2025):

Logging the Disconnects of Remote Sessions

That is in mesh events, just not surfaced in TRMM.

Additionally, was after disconnect and reconnect audits so i can report overall

Mesh also has this but only for 7 days.

Because mesh (websocket) and TRMM (NATS heartbeat) have two different methods for "connected" it's complicated.

@silversword411 commented on GitHub (Feb 18, 2025): > Logging the Disconnects of Remote Sessions That is in mesh events, just not surfaced in TRMM. > Additionally, was after disconnect and reconnect audits so i can report overall Mesh also has this but only for 7 days. Because mesh (websocket) and TRMM (NATS heartbeat) have two different methods for "connected" it's complicated.