Report Workflow

The Report view performs a server-wide scan and evaluates service health using assertion checks.

What happens during a run

1. Service discovery: Quetzly Pro crawls folders and services from the provided server URL.
2. Per-service checks: It requests each service metadata and runs type-specific assertions.
3. Result classification: It marks each service as Healthy, Warning, Critical, or Unsupported.
4. Aggregation: It computes totals, outage counts, and average response times.

Status meanings

• Healthy: All checks passed.
• Warning: Reachable, but one or more non-critical checks failed.
• Critical: Service unreachable or critical checks failed.
• Unsupported: Service type currently not covered by deep checks.

Common checks

Depending on service type, checks include:

• Reachability and HTTP status.
• Presence of layers and tables.
• Spatial reference and extent consistency.
• Export/query behavior for map and feature services.

Sorting and filtering

In the Service Audit table, you can:

• Sort by service name, type, status, failed checks, and response.
• Filter by status category for triage workflows.

Practical triage pattern

1. Filter to Critical first.
2. Open each failed service and review failed checks.
3. Then review Warning services for data quality or configuration drift.
4. Re-run after fixes to confirm recovery.