plain-prompt
Diagnose MySQL replication lag
Interpret replica threads, source position, relay log, and workload symptoms.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI
Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
Fill variables
Values stay in this browser tab and are not stored.
Generated asset2 required field(s) must be completed
Objective: Identify whether lag is receive-side, apply-side, or reporting ambiguity.
Context: Do not skip transactions or reset replication automatically.
Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.
User request:
Topology/version:
{{environment}}
Replica status and metrics:
{{evidence}}
Diagnose lag.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
Replica_IO_Running Yes; Replica_SQL_Running Yes; Seconds_Behind_Source 1840; SQL thread state Applying batch
Expected result
Replication receives events but the applier is behind. Compare apply throughput, long transactions, and storage latency; do not treat Seconds_Behind_Source alone as a complete measure.