Documentation for the work behind the service.
Guides based on the current E4S Monitor workflows, written for operators who need context before they act.
Choose a workflow, then follow the evidence.
Documentation describes the real control-panel capabilities and their boundaries. Where a provider, agent, entitlement, or registered asset is required, the guide says so.
Confirm the workspace, asset ownership, and operator permission before collecting a signal.
Review status, history, freshness, and coverage before treating a check as complete.
Use notes, reports, notifications, or audit events to leave a trace for the next operator.
Explore the library
Getting started with E4S
A practical path from workspace setup to the first registered asset.
Read guide →ServersAdding and understanding a server
How server health, agent state, and history fit together.
Read guide →WebsitesWebsite monitoring and TLS
Follow availability, redirects, response behavior, and certificate state.
Read guide →ServicesService discovery and manual checks
Keep service health visible beside the host that runs it.
Read guide →OperationsAlerts and notification preferences
Route a useful signal without alert fatigue.
Read guide →OperationsReports and PDF exports
Share scoped monitoring and security evidence.
Read guide →SecuritySecurity scans and findings
Understand Quick, Standard, and Agent coverage before acting on a finding.
Read guide →Remote workFleet Runner operations
Coordinate authorized work across registered infrastructure.
Read guide →Remote workTerminal sessions
Operate through a session that records the right boundary without recording secrets.
Read guide →PlatformPlugins and lifecycle safety
Install and operate trusted platform extensions.
Read guide →AccountWorkspaces, teams, and account security
Keep access scoped to the people and workspaces that need it.
Read guide →