Monitoring and administration

Botream shows what your robots are doing as it happens, keeps a record of every security-relevant action, and cleans up old history on its own; this page covers the dashboard, system health, the audit log and retention.

#Dashboard

The Dashboard is the first page after sign-in. It updates live whenever a run starts or ends, so you do not need to refresh it.

• Stat cards: Running now, Last 24 hours, Success rate, Average run time and Agents online (with the time of the next scheduled run).
• Runs per day: completed, failed and stopped runs.
• Agents: every agent with its live state and the task it is running, linked to the run.
• Trend: success rate and average duration per day.
• Recent runs and Most failures.
• Selector health: how captured elements behaved in recent runs.

Choose 7 days, 14 days or 30 days at the top right. For a card-by-card description, see Running tasks.

For a single run, open it from Executions to follow its live log and see its failure details. For a single agent, see the Agents card here or Administration → Agents; see Agents.

#System health

Administration → System health (See system health permission) checks the parts of Botream Server every 10 seconds; Check now checks at once. A banner sums up the result: All systems are working, Some parts need attention or The database is unreachable.

Each component shows Healthy, Degraded, Down or Disabled.

Note: When the scheduler is down (usually because the database cannot be reached), schedules do not fire until it recovers, which it does by itself. Everything else keeps working. See Schedules.

Tip: For a load balancer or an external monitoring tool, the server also answers a minimal health check that needs no sign-in. See API.

#Audit log

Administration → Audit log (See the audit log permission) lists security-relevant actions, newest first: sign-ins, changes, credential use and administration.

Each entry shows When, the Action, the User (or system), the Target (for example Vault #3), a Summary of its details and the IP address. Expand an entry to see all its details. Failed and denied actions are highlighted in red, deletions and deactivations in amber.

#Filters

• Search id, details or IP: matches the target's id, the details text or the IP address.
• Any action: one action type.
• Any target: one target type, such as User, Vault or Execution.
• A date range.

#What is logged

Audit entries never contain passwords, tokens or other secret values. A changed secret setting, such as the SMTP password, appears as (changed).

Tip: To find out who used a credential, filter Any action by Credential access and search for the vault or credential name.

#Retention

Botream deletes old history automatically. Administrators set the periods in Settings:

The cleanup runs every 6 hours. To run it at once, click Clean up now on the Executions card of the Settings page and confirm; the result tells you how many executions, log lines and audit entries were deleted. Running executions are never deleted.

Warning: Deleted history cannot be restored. Back up the database if you need older records; see Upgrade and backup.

To keep the database smaller, you can also turn off Keep debug log lines: Debug lines sent by agents are then neither stored nor streamed, while info, warnings and errors are always kept.

#Selector health

Selector health (Edit tasks permission) shows how the element commands of recent runs found their elements: healthy, found by a fallback, healed, drifting or broken. Drifting selectors still work, but their element changed: re-capture them before they break. A daily email report can be sent to the addresses in Daily selector health report under Notifications.

See Finding elements reliably for the full page and what to do about each status.

#Other administration pages