These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Server Monitoring
- Integrations
Integrations
Connect observation sources while keeping the event receipt separate from response work.
- Server Monitoring
- Availability probes
- Server telemetry
- Log sources
- Deployment systems
- Event intake
Systems to connect
- Availability probes. Supply check time, success, latency, probe location and service reference.
- Server telemetry. Supply sample time and CPU, memory and free disk readings for a known asset.
- Log sources. Associate a stream with its service and preserve the source endpoint and retention setting.
- Deployment systems. Record the release version, environment, deployment time and outcome against the service.
- Event intake. Retain provider, external event identifier, receipt time, payload hash and disposition.
How connections are governed
Choose the service and asset mapping before accepting external observations. Review rejected and failed receipts so an intake problem is not mistaken for a healthy service. Keep the source event identifier stable across retries and preserve the time supplied by the source. Assign an operator to review changes in field mapping when a provider changes its payload. The incident remains the team’s investigation record, with an assignee and updates distinct from the incoming event.
Set up Server Monitoring your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.