Monitoring and continuity
Global views
Netter administrators open global dashboards from the portal's monitoring link. They cover availability and inference, host and sensors, accounting and exports, operational logs and APM.
Company views are separate and limited to authorized tenants. Customers do not receive global infrastructure, log or sensor views.
Read the signals
| Signal | Meaning |
|---|---|
| Requests, errors and duration | API/portal experience and service health |
| Reserved credit and uncertain usage | Accounting work to resolve, separate from provider balance |
| Notification/export queues | Accepted, retrying or failed deliveries |
| CPU, memory and disk | Host capacity and resource pressure |
| Sensors unavailable | VPS does not expose sensors; not a zero temperature |
| Traces and spans | Operational request chain without prompt content |
Telemetry does not replace the accounting journal. Trace sampling may reduce collected traces without reducing the required completion logs.
Observability configuration
Use Sistema e sicurezza groups for metrics, logs, traces, resources and storage. Observability destinations are separate from customer S3 archives and other application storage.
Initial catalog values retain metrics for 15 days and logs/traces for seven days; check the values actually applied. Local buffers and persistent queues are bounded and cannot guarantee indefinite delivery through a prolonged outage.
Backup and restore
The supported PostgreSQL backup design uses pgBackRest and an encrypted external destination. Activation requires configuration, accessible storage and a restore test. An available settings page does not establish that backups are active.
Retain verification evidence and measure recovery targets on the actual system. A single VPS remains a single point of failure. Database backup does not replace fiscal retention, customer S3 policies or identity management.
Changes and releases
Review differences and affected services before releasing. Keep rollback snapshots and coordinate the configuration agent with deployment. Application bundles must preserve persistent data, credentials, installed models and volumes.
Verify the changed behavior afterward: completed authentication, authorized request, public routing and relevant accounting. Private access and recovery procedures remain in repository operations documentation.