Starting point
Application errors rise in the payments service after a deployment.
An alert tells you something has failed, but not why. Operate checks the connected logs, code and records, explains what it found and suggests a change for an engineer to review.
An error alert identifies a symptom. Finding the cause still requires someone to reconstruct the release, read logs, check production state and rule out other explanations. That work interrupts the team even when the eventual change is small.
Start with an alert source and the relevant service repository. Add a database connection where production records help distinguish causes. The investigation depends on available evidence; a plausible explanation still needs review.
Review deployment and access boundariesIllustrative example. Findings depend on connected systems and available evidence. Proposed changes require engineer review.
Application errors rise in the payments service after a deployment.
Engineering receives the evidence and a proposed retry policy. It checks whether the change fits the service and applies it through its normal review process.
The retry path immediately repeats requests during provider timeouts. The investigation links the log pattern with the relevant code.
- retry: immediate+ retry: exponential_backoff+ max_attempts: 3Illustrative artifact. Review before applying changes.
Connect the systems used in a problem your team has already solved. Ask Operate to investigate it, then compare the answer with yours. Check the evidence and the suggested change before using it for more work.
Explore the production workspaceMonitor adds proactive error monitoring at $299 per workspace per month. Human-triggered bot investigations are available on Free and Investigate.
Operate runs on your own AI model, your provider account or a model you host, with no Operate token charge.
Compare plansNo. Your monitoring tools continue collecting signals and raising alerts. Operate uses connected sources to investigate the cause and propose a change.
Operate proposes changes for engineer review. Your team decides what to apply through its normal release process. Review each integration’s credentials and permissions before connecting production systems.
Choose a past incident or controlled test whose cause your team knows. Record the connected sources, incident time window and expected evidence. Keep the known answer out of the investigation prompt. Review the explanation, cited evidence, missing sources and proposed patch separately. Run the real repository checks before accepting a code change. An engineer decides what ships.
Use Operate agents to review database performance, investigate expensive query patterns and propose changes with supporting query and code evidence.
Explore this workflowOperate helps teams review infrastructure usage, identify idle capacity and investigate cost recommendations with connected evidence.
Explore this workflowReview production access configuration with Operate agents. Investigate exposure risks and inspect proposed configuration changes before applying them.
Explore this workflowUse Operate in Slack or Microsoft Teams to investigate unexpected product behavior using logs, code and production data, with evidence and proposed next steps.
Explore this workflowOperate automatically generates verified knowledge articles from root causes. Teams can manually manage, edit and verify articles for future production investigations.
Explore this workflowNeed engineers to help handle the work? Explore managed operations.