monitor-omo-services

Name: monitor-omo-services
Availability: InStock
Author: ridopark

Monitor omo-core trading system logs and database consistency for anomalies.

1|Updated Mar 4, 2026

Search Tags:#monitoring #log analysis #anomaly detection #database health #trading system #omo-core

Ready to run

npx skills add https://github.com/ridopark/oh-my-opentrade --skill monitor-omo-services

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: monitor-omo-services
Source: https://github.com/ridopark/oh-my-opentrade/tree/main/.claude/skills/monitor-omo-services
Command: npx skills add https://github.com/ridopark/oh-my-opentrade --skill monitor-omo-services

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill continuously monitors the omo-core trading system's logs and database for errors, warnings, and inconsistencies, ensuring system stability and detecting potential issues before they impact trading.

Core Features & Use Cases

Real-time Log Analysis: Scans Loki logs for critical errors, warnings, and specific anomalies.
Database Health Checks: Verifies data integrity, checks for position drift against the broker, and monitors for stuck orders or stale market data.
System Uptime Monitoring: Detects frozen bots and ensures data is being processed for all expected symbols.
Use Case: When you suspect something is wrong with the trading bot, use this Skill to get a comprehensive overview of its health, pinpoint errors, and identify any discrepancies in trades or positions.

Quick Start

Start monitoring the omo-core services by asking to monitor logs and check database health.

Frequently Asked Questions about monitor-omo-services

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I monitor trading system logs for errors and warnings?▼

To monitor trading system logs, query Loki logs to scan for critical errors, warnings, and specific anomalies. This detects frozen bots, stuck orders, and market bar gaps, providing actionable insights for system stability and trading performance.

How do I check database consistency and detect position drift in a trading bot?▼

Check database consistency by verifying data integrity and comparing internal position records against the broker. This detects position drift, stuck orders, and stale market data, ensuring the trading system maintains accurate state and stability.

What is the best way to detect frozen bots and market data gaps?▼

Detect frozen bots and market bar gaps by continuously monitoring system uptime and verifying that data is processed for all expected symbols. Analyzing Loki logs and database health identifies when bots stop processing or miss expected market data.

Can I use database health checks to find stale market data and stuck orders?▼

Yes, database health checks can find stale market data and stuck orders by verifying data integrity and monitoring for processing inconsistencies. This ensures data is updated for all expected symbols and identifies orders that fail to execute properly.

Why does my trading bot show position drift against the broker?▼

Position drift occurs when internal database records disagree with the broker's actual positions. Running database consistency checks identifies these discrepancies, along with stuck orders and data integrity issues, to restore system stability.

How do I get a comprehensive overview of trading bot health and anomalies?▼

Get a comprehensive overview of trading bot health by analyzing system and economic metrics through Loki log queries and database consistency checks. This reports anomalies like frozen bots, position drift, and market bar gaps for trading performance.