blueplane

Manage Blueplane telemetry server lifecycle and logs via server_ctl.py, Redis, and SQLite.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/blueplane-ai/bp-telemetry-core --skill blueplane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueplane
Source: https://github.com/blueplane-ai/bp-telemetry-core/tree/main/.claude/skills/blueplane
Command: npx skills add https://github.com/blueplane-ai/bp-telemetry-core --skill blueplane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides concise, actionable operational guidance to manage the Blueplane telemetry processing server so developers can start, stop, restart, monitor, and troubleshoot the service without guesswork or manual log hunting.

Core Features & Use Cases

  • Server lifecycle management: Clear commands and options for starting in foreground or daemon mode, stopping gracefully or forcefully, and restarting after code or config changes.
  • Monitoring & diagnostics: Log locations, common grep/tail commands, status checks, Redis stream and consumer group inspection, and SQLite queries for validating data ingestion.
  • Development and production workflows: Steps to restart after pulls, run tests, verify health, and recover from stale PID or hung processes.
  • Use Case: After deploying a code change to the processing logic, restart the server in daemon mode, verify Redis stream lengths and consumer groups, and inspect the last 100 log lines for errors to confirm normal operation.

Quick Start

Restart the Blueplane server as a background daemon, then display the last 50 lines of the server log and check the server status for verbose health details.

Frequently Asked Questions about blueplane

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

FAQPage Schema
How do I restart a telemetry processing server as a background daemon?

To restart the telemetry processing server as a background daemon, use the server_ctl.py CLI to issue a restart command. This gracefully stops the active process and starts a new daemon instance, applying recent code or configuration changes automatically.

Where are telemetry server logs stored for troubleshooting?

Telemetry server logs are stored under the ~/.blueplane directory. You can apply common grep or tail commands to these log files to monitor live output and troubleshoot processing errors or diagnose server health issues.

How do I check Redis stream lengths and consumer groups for telemetry data?

You can check Redis stream lengths and consumer groups by executing Redis CLI commands against your telemetry streams. This inspects data ingestion queues and verifies that consumer groups are actively processing telemetry events without lag.

How do I verify telemetry data ingestion in a SQLite database?

Verify telemetry data ingestion in a SQLite database by running sqlite3 queries against the local telemetry database file. This validates that processed events are correctly stored and confirms successful data pipeline execution.

What is the best way to recover a telemetry server from a stale PID or hung process?

Recover a telemetry server from a stale PID or hung process by using the server_ctl.py CLI to forcefully stop the unresponsive service. After termination, start a fresh daemon instance to restore normal operational workflow.