An operating context, not a single status badge
Registered servers, websites, and services are organized by workspace. Monitoring checks produce current state and history; notifications route meaningful changes; reports preserve evidence for review. Roles and workspace membership determine which data and actions a user may access.
How E4S fits into a response
- Register only infrastructure your organization owns or is authorized to operate.
- Confirm the first successful check or agent heartbeat.
- Compare a warning with check freshness and earlier observations.
- Route the alert to the relevant operator and review the evidence.
- Use an authorized remote operation only after confirming target and scope.
Coverage depends on installation settings, license, role, and agent capability. The getting started guide explains the initial sequence.
One workflow, separate responsibilities
The East4Serv website manages accounts, requests, commercial records and support. Infrastructure Control supplies the monitoring observations and advanced operations available to an authorized workspace. A client can use the website portal to review their business relationship without receiving a master Monitor credential.
Start with the relevant view
- Monitoring explains asset state, check history and missing-signal context.
- Platform capabilities separates monitoring from restricted remote operations.
- The marketplace contains published products and staff-reviewed order paths.
- Documentation describes supported workflows and account setup.
Plan limits and advanced permissions vary by entitlement. A route or screen existing in the platform does not mean every customer can use it. Ask which workflow fits your infrastructure.