How fast is the diagnosis?

Most diagnoses complete in under 60 seconds from the moment the CloudWatch alarm fires to the moment the message arrives on your phone. Complex cases (large log volumes, multi-region resources) can take up to 2 minutes.

What if the diagnosis is wrong?

Reply INVESTIGATE for a deeper analysis with more log context, or RESOLVE to mark the diagnosis correct. ConvOps tracks accuracy over time and improves the diagnosis prompt based on what you mark as correct or incorrect.

Can ConvOps actually fix the issue, not just diagnose it?

Optionally, yes. By default ConvOps uses read-only access — the diagnosis includes copy-paste AWS CLI commands you run yourself. If you grant a second IAM role with limited write permissions, you can reply with the number of a suggested fix and ConvOps will execute it after confirming. Most teams start with read-only.

Does this work with PagerDuty?

Yes. ConvOps sits between CloudWatch and PagerDuty. When an alarm fires, ConvOps diagnoses first, then forwards the enriched alert to PagerDuty with the diagnosis attached. PagerDuty handles routing and escalation. You see better alerts.

What if I don't want to use WhatsApp?

Slack works identically. Same diagnosis, same reply commands. You can use either or both on the same alert.

Does ConvOps replace my monitoring?

No. ConvOps Diagnose works on top of whatever monitoring you already have — CloudWatch, Datadog, New Relic. When their alarms fire, we diagnose. We don't replace the alarms; we make them useful.

ConvOps Diagnose · Root cause when alarms fire

Your phone buzzes. The diagnosis is already there.

The moment a CloudWatch alarm fires, ConvOps Diagnose reads your logs, CloudTrail, and resource state — then sends a plain-English root cause and numbered fix options to WhatsApp or Slack. Reply with a number. Go back to sleep. If you want to catch anomalies before they alarm, see ConvOps Watch.

Start free trial →See an example →

Included in all paid plans. First diagnosis in under 60 seconds from alarm fire.

ConvOps

online

TODAY

🚨 PROD-Lambda-Function-Errors fired

prod-api-order-processor · us-east-1 · production

Root cause (91% confidence) Memory exhaustion — Lambda hitting 512 MB limit under burst load. 340+ invocations timed out.

[ERROR] Task timed out after 900.00s
MemorySize: 512 MB · Used: 510 MB
Errors/min: 47 ↑ (threshold: 5)

💥 Impact: ~340 orders unprocessed in last 15 min

Fix steps:

1 → Increase Lambda memory to 1024 MB

2 → Enable SQS dead-letter queue

3 → Reduce batch size: 100 → 25

Reply: ACKNOWLEDGE · RESOLVE · SNOOZE 30

convops.io · Alert #lmb-472903:14

ACKNOWLEDGE

03:15✓✓

✓ Acknowledged · 03:15 AM

Auto-escalating to on-call in 20 min if not resolved. Reply RESOLVE when fixed.

03:15

The 3am ritual

CloudWatch sends you a wall of JSON. You're not awake yet.

A CloudWatch alarm tells you something crossed a threshold. It doesn't tell you why. So you open the AWS console on your phone, squint at four dashboards, scroll through CloudTrail, dig for log groups, and try to reconstruct what happened — all while half-asleep and increasingly aware that whatever you do next, you'll be doing it groggy.

First diagnosis

under 60 seconds from alarm fire

Reads automatically

logs, CloudTrail, and resource state

Delivered to

WhatsApp or Slack — your choice

One alarm. One answer.

Here's what CloudWatch sends — and what ConvOps sends instead.

What CloudWatch sends you

Raw noise. No context.

⚠ ALARM — us-east-1
Source: AWS CloudWatch
Time: 02:17 AM
Alert: CPUUtilization > 80%
Service: api-service (us-east-1)
Value: 96.4%

That's it. Raw. No context. No fix. Just noise. A wall of JSON. You still have to open CloudWatch, correlate four dashboards, and guess at the root cause — at 3 am.

What ConvOps sends you

Diagnosis. Next step. Done.

ConvOps

online

TODAY

🚨 PROD-Lambda-Function-Errors fired

prod-api-order-processor · us-east-1 · production

Root cause (91% confidence) Memory exhaustion — Lambda hitting 512 MB limit under burst load. 340+ invocations timed out.

[ERROR] Task timed out after 900.00s
MemorySize: 512 MB · Used: 510 MB
Errors/min: 47 ↑ (threshold: 5)

💥 Impact: ~340 orders unprocessed in last 15 min

Fix steps:

1 → Increase Lambda memory to 1024 MB

2 → Enable SQS dead-letter queue

3 → Reduce batch size: 100 → 25

Reply: ACKNOWLEDGE · RESOLVE · SNOOZE 30

convops.io · Alert #lmb-472903:14

ACKNOWLEDGE

03:15✓✓

✓ Acknowledged · 03:15 AM

Auto-escalating to on-call in 20 min if not resolved. Reply RESOLVE when fixed.

03:15

Root cause already identified. Suggested fix already written. Reply 1 and go back to sleep.

How it works

From alert to fix in four steps.

ConvOps Diagnose runs automatically the moment a CloudWatch alarm fires — no manual trigger, no dashboard to open. Deploy a read-only CloudFormation template once, and every future alarm arrives with root cause already attached.

Connect AWS

Drop in a CloudFormation template. 2 minutes. No CLI required. Read-only access by default.

Alert fires

CloudWatch triggers ConvOps the moment a threshold is breached. Not after you've been paged.

AI investigates

While you're still waking up, ConvOps has already read the logs, checked what changed, and worked out why it broke.

You reply

Get the diagnosis on WhatsApp or Slack. Reply with a number. ConvOps confirms before acting.

Your alarm, your words.

Reply to any alert with plain English. No dashboards, no runbooks.

ACKNOWLEDGE

You're on it. Stops reminder notifications.

INVESTIGATE

Triggers deep-dive analysis with full log context.

RESOLVE

Marks it resolved and logs time to fix.

ADJUST

Gets AI-recommended threshold change. Reply YES to apply.

SILENCE

Suppresses a noisy alarm permanently. You can WATCH to re-enable.

WATCH

Re-enables a silenced alarm.

STATUS

Get a live summary of active alarms and diagnoses.

What ConvOps Diagnose reads

Every signal your alarm needs.

When an alarm fires, ConvOps Diagnose investigates in parallel — pulling whatever signals are relevant to the metric that triggered it. Most diagnoses complete in under 60 seconds.

CloudWatch Logs

relevant log streams from the affected resource, parsed for exceptions, error codes, and unusual patterns

CloudTrail

recent API calls that may have caused the issue (deploys, config changes, IAM modifications)

Resource state

current configuration of the affected resource (instance state, autoscaling group, task count, parameter group)

Related metrics

other CloudWatch metrics on the same resource that may explain the trigger

GuardDuty and Security Hub

active findings that may be the cause

AWS Health

region or service-wide incidents that may be the cause

Coverage

What ConvOps Diagnose handles.

ConvOps Diagnose works with CloudWatch alarms on any of these services. Connect your AWS account once — every alarm on every resource is automatically eligible.

Compute and containers

EC2
ECS (Fargate and EC2-backed)
Lambda
EKS

Database and cache

RDS (all engines)
Aurora
DynamoDB
ElastiCache

Network and edge

ALB / NLB
API Gateway
CloudFront

Storage and messaging

Plus security findings from GuardDuty, Security Hub, Inspector, and Trusted Advisor.

Pricing

Included in every paid plan.

ConvOps Diagnose is included in both tiers — free on Individual, $49/mo on Growth. Unlimited diagnoses. No per-investigation pricing. WhatsApp and Slack both supported on all tiers.

See full pricing →

Common questions about ConvOps Diagnose.

Answers about diagnosis speed, accuracy, remediation permissions, and how Diagnose works alongside PagerDuty, Slack, and WhatsApp.

Connect AWS. First diagnosis in under 10 minutes.

Read-only CloudFormation template. No CLI. No agent. Revoke access from your IAM console in 30 seconds.

Start free trial →Run free audit first →

Individual is free forever. Growth $49/mo. Cancel any time.