Observability
Zenifra observability helps you follow project behavior after deployment. Log and metric availability varies according to the subscribed plan.
HTTP projects
For HTTP projects, Zenifra provides visibility into:
- application logs
- CPU usage
- RAM usage
- storage usage
- number of HTTP requests received by the application
- network traffic by time window
- distribution by HTTP status
- most accessed routes and top user agents
- P95 latency when available
- request events with raw source IP
These features are available on Premium or higher plans.
Granularity and update window
Logs and metrics are viewed by instance when the project has more than one instance.
| Resource | Expected update |
|---|---|
| Logs | up to 60 seconds |
| Resource metrics | up to 5 minutes |
| HTTP network traffic | up to 5 minutes |
Use this update window when investigating recent deployments, traffic spikes, or behavior immediately after a restart.
HTTP network traffic
The network view aggregates the project's HTTP behavior across 5 min, 1 h, 6 h, 24 h, and 7 day windows. Use these filters to compare recent traffic with longer patterns without mixing data from different periods.
The panel shows:
- total requests in the period
- inbound and outbound application data
- P95 latency when available
- distribution across
2xx,3xx,4xx, and5xxresponses - most accessed routes by method and path
- top user agents
- individual request events with raw source IP, sanitized route, status, and latency
When you click a status class, such as 4xx or 5xx, the console opens a drill-down with routes, user agents, and request events associated with that filter. This helps investigate client errors, server failures, involved source IPs, and high-volume endpoints.
Privacy: Request events display raw source IPs to users with access to the project's metrics and are retained for up to 7 days. Query strings and referrers are not stored in this view.
Databases
For databases, Zenifra shows metrics for:
- CPU
- RAM
- storage
These metrics are available on Premium+ plans and can appear per database project and by instance or replica.
Features not currently available
These items are not currently available as documented capabilities:
- per-application uptime
- automatic autoscaling
If these data points are required for a contract or critical operation, validate availability in the console and with support before depending on them.
Daily usage
Use logs to understand build failures, startup errors, application exceptions, and configuration problems.
Use CPU, RAM, storage, and HTTP request metrics to decide when to increase instances, change plans, review queries, optimize cache, or investigate abnormal usage.
Next steps
FAQ
Why do data not appear immediately?
Logs and metrics have an update window. Wait a few minutes after deployment, restart, or traffic spikes before concluding there is no data.
Do metrics replace external monitoring?
Not necessarily. For critical operations, combine Zenifra metrics with alerts and application monitoring.
Is automatic autoscaling available?
No. The documented scaling flow is manual instance and plan adjustment.