database-migrations-migration-observability
Monitor Database Migrations in Real Time
Database migrations can fail without clear signals about lag, throughput, or errors. This skill designs CDC monitoring, metrics, dashboards, and alerts for migration workflows.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "database-migrations-migration-observability" from https://skillstore.io/skills/sickn33-database-migrations-migration-observability.md and its manifest at https://skillstore.io/api/skills/sickn33-database-migrations-migration-observability/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "database-migrations-migration-observability". Recommend monitoring for a PostgreSQL CDC migration.
Expected outcome:
- Track connector state, source log position, consumer lag, event throughput, and failed records.
- Alert when replication lag exceeds 60 seconds for five minutes or connector failures persist.
- Dashboard migration progress, per-table throughput, lag percentiles, and recovery status.
Using "database-migrations-migration-observability". Plan alerts for a MongoDB migration.
Expected outcome:
- Warn when throughput falls below half of the expected rate.
- Escalate when errors exceed one percent or progress remains unchanged.
- Resolve alerts only after throughput and error rates remain healthy.
Using "database-migrations-migration-observability". Add migration checks to continuous integration.
Expected outcome:
Start monitoring before the migration, run the migration, then fail the workflow when lag or error thresholds remain unhealthy.
Security Audit
Medium RiskAll 11 external-command alerts are false positives caused by Markdown fences or JavaScript template literals. Three examples perform outbound POST requests, including one that sends a Grafana bearer token to a configured endpoint. No prompt injection or malicious intent appears, but users should validate destinations and use least-privilege credentials.
Confirmed security concerns (1)
Capability review items (3)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (11)
🌐 Network access (3)
🔑 Env variables (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-database-migrations-migration-observability/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-database-migrations-migration-observability?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-database-migrations-migration-observability?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-database-migrations-migration-observability/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-database-migrations-migration-observability.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). database-migrations-migration-observability security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-database-migrations-migration-observability/audits/5BibTeX citation
@techreport{sickn33-sickn33-database-migrations-migration-observability-2026,
author = {sickn33},
title = {database-migrations-migration-observability security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-database-migrations-migration-observability/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "database-migrations-migration-observability security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-database-migrations-migration-observability/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-database-migrations-migration-observability:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Instrument a Live Migration
Add logs, progress metrics, lag measurements, and error counters to an active database migration.
Monitor a CDC Pipeline
Design Debezium and Kafka visibility for event throughput, consumer lag, and source-to-target delay.
Build Migration Alerts
Define dashboards, thresholds, notifications, and CI health gates for production migration operations.
Try These Prompts
Recommend essential metrics for a [database type] migration. Include progress, duration, lag, throughput, failures, and practical alert thresholds.
Design monitoring for a Debezium pipeline from [source] to [target] through Kafka. Cover connector health, lag, throughput, errors, and recovery signals.
Create a Grafana dashboard and alert plan for [migration]. Use Prometheus metrics and separate warning, critical, and recovery conditions.
Design end-to-end observability for [migration architecture]. Include metric definitions, label controls, CDC validation, anomaly detection, dashboards, alerts, CI gates, and rollback signals.
Best Practices
- Define baseline throughput and lag before choosing alert thresholds.
- Use bounded labels to prevent excessive Prometheus metric cardinality.
- Test dashboards, alerts, credentials, and rollback signals in a staging environment.
Avoid
- Do not expose database credentials, API tokens, or webhook URLs in logs and metrics.
- Do not treat event counts alone as proof that source and target data match.
- Do not deploy untested alert thresholds that can hide failures or create alert noise.