nt8-log-monitor_skill

This skill autonomously monitors NinjaTrader 8 logs and traces to detect errors and crashes, ensuring healthy deployments and quick issue detection.

C#

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill mkalhitti-cloud/universal-or-strategy --skill nt8-log-monitor

SKILL.md1.8 KB

Overview

This skill autonomously monitors NinjaTrader 8 log and trace files to detect errors, rejections, and crashes affecting MES/MGC strategies. It locates the most recent logs and trace files, scans for key failure indicators, and highlights instrument-specific events. The goal is rapid health checks after deployments or when suspected order/connection issues occur.

How this skill works

The skill searches the project root for the latest .txt logs and brokerage/Rithmic trace files, then parses them for keywords like Rejected, Error, Exception, and Termination. It filters results for instrument identifiers (MES, MGC) and timestamps recent events to surface critical issues. Scripts are provided to automate finding latest logs and scanning for errors, and the skill can be invoked as part of a post-deployment health check.

When to use it

Immediately after deploying or updating the Master Strategy to verify initialization completed without errors
When an order is suspected to have been rejected or a stop/exit did not execute
If connection instability or Rithmic disconnects/timeouts are observed
As a routine health check during monitoring windows or after automated restarts
Before escalating issues to support or rolling back a deployment

Best practices

Run the log scan within five minutes of deployment to catch initialization failures
Include instrument filters (MES, MGC) to reduce noise and focus on relevant trade events
Combine log scans with timestamp checks to correlate errors with recent trading activity
Automate the script in CI/CD or deployment hooks so health checks run consistently
Keep archive retention settings reasonable so required trace files remain available for diagnostics

Example use cases

Post-deployment verification: run the scan to confirm no Termination or Exception entries after a strategy update
Order troubleshooting: detect Rejected messages and capture related trace lines for root cause analysis
Connection diagnostics: scan trace files to find Rithmic disconnects, timeouts, or reconnection attempts
Automated alerting: integrate the scan into monitoring to notify operators when Error or Termination keywords appear
Investigations: collect and export matching log segments for support tickets or post-mortem reviews

FAQ

It targets the project root log/ and trace/ locations, locating recent .txt logs and brokerage/Rithmic trace files for analysis.

What keywords does the scanner look for by default?

Default keywords include Rejected, Error, Exception, and Termination; you can extend this list to include instrument tags like MES or MGC.

How quickly should I run this after deployment?

Run the scan within five minutes of deployment to catch startup or initialization errors that happen immediately after strategy load.