Questions, answered

Click Get started, then use Proto to configure Log Management & Analysis for your business. Begin with one service, its owner, one source stream and a representative alert-to-incident case.

It keeps a stream name, source endpoint, retention days and the service it supports. Use the source endpoint when coordinating setup with the observability team.

An alert carries a query definition, observation window, match count, stream and triage status. The team can open a separate incident for service response when needed.

Set up a connection to the observability system that stores and searches them. The stream record identifies the source used in the team’s operating workflow.

The response workflow acknowledges a new incident or authorized inbound event and records the actual acknowledgment time. The assigned Incident Responder checks the work. Incident updates retain the author and occurrence time of later observations.

A Change Approver reviews the service, risk, planned window and rollback plan while the change is in review. Approved work then moves into implementation and verification.

A problem record holds the service, owner, problem statement, root cause and investigation status. Use it for continuing cause work alongside incidents.

Requests capture a requester, request type, due date and approval and fulfillment path. Incidents capture a response to a service issue with priority, assignee and response times.

Find the processing receipt by external event identifier. Its processing status distinguishes received, applied, rejected and failed outcomes.

Use incident opening, acknowledgment and resolution times, together with service and priority, to compare the recorded intervals.