server icon indicating copy to clipboard operation
server copied to clipboard

[ENHANCEMENT]: Agent status improvements

Open ObsidianOracle opened this issue 7 months ago • 3 comments

Description

If you activate an Agent it is displayed as "active". If you kill the agent waiting for a task with ctrl + c it is still displayed as active. In this case it should be changed to inactive immediately.

ObsidianOracle avatar May 20 '25 14:05 ObsidianOracle

Implement it for killing the agent.

ObsidianOracle avatar May 28 '25 08:05 ObsidianOracle

Agent Details show the graphs (gpu-temp, -util, cpu-util) of the current task (as expected). If the agent is idling, it shows the data of the last task (which could be yesterday or days ago). I would expect to see the current data as well, even when there is no job running. (That is probably due to the fact, that the info stems from hashcat and when there is no task running, there is no hashcat and no data. But my expectation would still be, that you can see the current temperatures as well. After a fresh install, when there are no tasks yet, the graphs are completely missing.)

In addition to the active-information on an agent a information “online” (for example) would be nice, which should be configurable in the settings. For example if it is set to 10 mins and an agent had its last activity longer ago than 10 minutes, it is labeled “offline”. On the dashboard it should be shown as well (Active/Online/Total Agents).

Furthermore I was not able to differentiate immediately between task that is stopped due to agents disconnecting on error and task that was stopped due to all hashes being cracked in another task. Task causing agent errors could be more clearly marked in the task window.

As a workaround we should add improvements that the agent status is displayed correctly.

ObsidianOracle avatar Sep 03 '25 12:09 ObsidianOracle

This enhancement should be done by renaming/rebranding the isActive flag we have to isEnabled (as this is what the active currently really is). It determines if the agent should be enabled or not.

And additionally then, add a separate way to show agents as active or inactive (e.g. based on their last request to the server). If then an agent is killed or died, it would show that it is not active anymore, even though it would still be enabled for example.

s3inlc avatar Oct 21 '25 12:10 s3inlc