Monitoring, security and operations.
With the pieces connected.

Servers and containers

Connect host health with the services it runs.

• Linux and Windows agents with heartbeat and system inventory.
• CPU, memory, disk and service observations to identify resource pressure.
• Docker inventory and container context linked to its server.
• Favorites, tags and per-asset monitoring controls.

Collection respects agent permissions; inaccessible modules expose their coverage.

IIS, .NET and SQL Server

Windows stack visibility from server to application.

• IIS sites, bindings, pools and associated certificate metadata.
• Installed runtime versions and NuGet packages identified in deployment manifests.
• WebForms configuration observations and Windows update context.
• SQL Server inventory and optional read-only database and backup-status queries.

An installed runtime does not establish which runtime an application loads. Inspection does not transmit connection strings or private keys.

WordPress and its components

Put versions, changes and findings in each site's context.

• Core, plugin and theme inventory with versions and observed updates.
• Site relationships to server, container and customer.
• User inventory and detection of new administrators after baseline when WP-CLI is enabled.
• On-demand investigation and file integrity where collection is enabled.
• Change-plan preparation with checks and task follow-up.

Premium licensing and compatibility are reviewed separately. Plans do not automatically execute updates.

GitLab and applications

Review application inventory alongside its operational environment.

• GitLab versions and update references according to the configured source.
• Applications linked to servers and customers, with details and related signals.
• Available component and deployment context for investigation.

Integrations use available evidence; they do not imply universal repository or pipeline access.

External sites, HTTP and certificates

Monitor applications hosted outside your servers too.

• HTTP checks with status, response time and error category.
• TLS observations and certificate-expiry tracking.
• External URLs grouped by customer, without an agent on the remote host.
• Manual HTTP/TLS checks kept separate from scheduled history.

A successful HTTP response measures endpoint availability; interactions are checked through functional profiles.

Functional checks

Extend checks to browser workflows defined for each site.

• Reviewed profiles for interactions such as navigation, menus or carousels.
• Per-device results, evidence and dependencies that could not be checked.
• Isolated runner with request, time and resource limits.
• Separation of observed failure, incomplete execution and unknown coverage.

Requires deploying the runner and reviewing and activating each site's profiles.

Vulnerabilities and integrity

Prioritize findings alongside the asset and supporting evidence.

• Correlation of components and versions with available vulnerability references.
• Severity, update and source-coverage context.
• File integrity monitoring at configured locations.
• PHP and .NET finding review where compatible evidence is available.

A version match is a signal to investigate; the platform does not certify a site as free from vulnerabilities or malware.

Logs and events

Investigate using records linked to servers and applications.

• Log console with source and time-window filters.
• Bounded Linux source and Windows event collection according to permissions.
• Syslog integration and detection rules for configured sources.
• Access to related logs from incident details.

Retention, permissions and sampling limits determine available history.

Alerts and incident investigation

Follow the path from the initial signal to evidence and follow-up.

• Prioritized alerts, deduplication and observed-recovery tracking.
• Incident workspace with timeline, HTTP observations, changes and related logs.
• Investigation notes, history and linked tasks.
• Email notifications, retries and maintenance silences according to configuration.

Temporal proximity supports investigation; it does not establish a root cause on its own.

Diagnostics, forecasts and AI

Turn technical signals into context your team can check.

• Diagnostics and recommendations based on available observations.
• Resource forecasts when sufficient history exists.
• Internal AI-assisted explanations referencing supplied evidence.
• Permission-controlled and audited request and result records.

AI requires additional configuration. Its explanations are reviewed by technicians and execute no commands or remediation.

Tasks, calendar and reports

Keep operational follow-up alongside assets needing attention.

• Tasks, assignees, priorities, due dates and work steps.
• Calendar of tasks, certificates and maintenance windows.
• Incident, backlog, task and functional-result reports.
• Access-controlled operational report HTML export.

Indicators describe recorded data; they do not attribute unmeasured cost or time savings.

Dependencies and service objectives

Understand shared asset context and how observed availability evolves.

• Server → application → container map based on recorded relationships.
• Impact navigation to related alerts and incidents.
• Per-application availability targets and 7- or 30-day windows.
• Sample coverage, unknown time and estimated remaining error budget.

Sharing a server indicates potential exposure. Objectives use HTTP samples and do not constitute a contractual SLA.

Backup visibility

Bring together available observations about backups and their infrastructure.

• SQL Server backup metadata when read-only querying is enabled.
• Backup-server health and capacity through the agent.
• Job context and evidence sources reviewed for each connector.

A file timestamp does not establish backup success. External-tool coverage and restore testing require specific integration and evidence.

Customers, permissions and audit

Give technicians visibility aligned with their responsibilities.

• Organization by customers, operational groups, favorites and tags.
• Roles, screen and action permissions, and asset restrictions.
• Monitoring pause and notification silences for planned maintenance.
• Audit history with actor, timestamp and recorded changes.
• Central Hub and outbound HTTPS agents for self-hosted deployments.

Authentication, permissions and connectors are configured for each deployment.

WordPress forensic analysis

Request a read-only investigation with retained evidence for review.

• Hub observation snapshot and fresh file inspection through the authorized agent.
• Component, integrity-change, event and finding summary with coverage and timestamps.
• Integrity-hashed snapshot and protected HTML report export.
• Requests and reports governed by specific permissions and audit.

This is a read-only operational investigation; a baseline or heuristic does not certify authenticity or absence of malware.