Read runtime evidence next to deployment history.
Check application health, resource use and logs alongside deployment history. Give the person investigating a failed or slow service a place to start.
- Demo project
- Apps
- catalog-service
Sample service page for catalog-service in Staging. It is degraded: 1 of 2 pods ready with 3 restarts, last exit OOMKilled. Memory averages 468 of a 512 Mi limit per pod and CPU averages 85 millicores. Pod events list a failed readiness probe and an out-of-memory restart.
Cloud monitoring
What you get
A view of the affected service, its resource consumption and its recent deployment context.
What you bring
- Applications and infrastructure connected to a Microtica project.
- Available metrics depend on the workload and the monitoring integration configured for it.
How it works
Know what happens before you start.
- 01
Open the service
Select the workload and environment. Review its current health, deployed revision and available CPU or memory information.
- 02
Inspect the evidence
Read application logs and events, then check recent deployments. Use the environment context to avoid comparing unrelated workloads.
- 03
Follow a signal or investigate
Use Signals to identify reported problems, or bring the available logs and deployment context into a Mica investigation.
Pod health and resource use
See ready pods, restarts, the last termination reason and average CPU or memory per pod when that data is available.
Events and logs
Inspect Kubernetes pod events for scheduling, image pulls, restarts and probe failures. Open the service logs or its deployment runs to investigate further.
“Microtica provided us with excellent guidance and support throughout the migration process, and the cloud platform has been a breeze to use since then. We are very thankful for the cost savings measures the platform provides.”
Access and control
Check coverage for your workload
A connected account is not a guarantee that every resource, trace or external monitoring source appears in Microtica. This page does not promise replacement of a full observability or SIEM stack.
Try it on one service.
Start free with a development project, or bring your setup to a demo.