Know which workload needs your attention.
See unhealthy pods, failed deployments and resource failures in your Microtica project. Connect team notifications, then open the affected workload to investigate.
- Demo project
- Signals
Sample Signals view listing four conditions to look at: catalog-service running with fewer pods in Staging, order-worker out of memory, a failed Development deploy and inventory-service restarts. Beside it, a team-channel message reports the failed Staging deploy with a link back to Microtica.
Alerts and signals
What you get
An identified workload and environment, with the current failure state and a path to its logs.
What you bring
- Connected applications or infrastructure with available health data.
- Add a Slack or Microsoft Teams webhook if your team needs deployment notifications in a channel.
How it works
Know what happens before you start.
- 01
Connect your team channel
Add a webhook in Integrations. The current interface supports deploy and alarm notifications in Slack, and build and deploy notifications in Microsoft Teams.
- 02
Check the current state
Use Signals to find pod readiness failures, crash loops, out-of-memory events, failed environment deployments and unreachable clusters.
- 03
Open the affected workload
Follow the service or environment context. Inspect logs and recent deployments, or ask Mica to help investigate the evidence.
Signals explain their source
A pod failure includes readiness or termination information. A deployment failure includes its reported status and reason when available.
Environment context
Filter signals to one environment so development and production issues can be reviewed in their own context.
“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
Current signals are not an incident archive
The current Signals view does not retain resolved signals. Channel notifications are separate from a complete on-call incident-management system.
Try it on one service.
Start free with a development project, or bring your setup to a demo.