pilot-log-analytics-setup

Deploy a four-agent log analytics pipeline with collector, parser, alerter, and dashboard.

7|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-log-analytics-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-log-analytics-setup
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-log-analytics-setup
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-log-analytics-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy a centralized log analytics pipeline across four agents to collect, parse, alert, and visualize logs.

Core Features & Use Cases

  • Collector aggregates logs from servers and applications and normalizes formats for unified search.
  • Parser extracts structured fields and tags events with severity for actionable insights.
  • Alerter detects anomalies and spikes to trigger timely alerts.
  • Dashboard provides full-text search, time-series visualization, and drill-down reports for health monitoring.

Quick Start

Select roles for collector, parser, alerter, and dashboard, install their skills, set hostnames, and initiate the setup.

Frequently Asked Questions about pilot-log-analytics-setup

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

FAQPage Schema
How do I set up a centralized log analytics pipeline across multiple hosts?

A centralized log analytics pipeline aggregates logs from distributed hosts by assigning agent roles for collection, parsing, alerting, and visualization to normalize formats and enable unified search.

What is the best way to collect and parse logs for anomaly detection in distributed environments?

Collecting and parsing logs for anomaly detection uses dedicated agents to extract structured fields, tag event severities, and identify spikes to trigger timely alerts across distributed environments.

How does a multi-agent observability setup handle data flows and peer handshakes?

A multi-agent observability setup handles data flows and peer handshakes by using defined protocols on port 1002 and 443, ensuring reliable data transmission and role-based skill composition across agents.

Can I deploy log visualization and alerting without specific external dependencies?

You can deploy log visualization and alerting without external dependencies by selecting internal agent roles for the dashboard and alerter, configuring hostnames, and initiating the setup manifest workflow.

What features does a log analytics dashboard provide for health monitoring?

A log analytics dashboard provides full-text search, time-series visualization, and drill-down reports to enable comprehensive health monitoring and actionable insights across aggregated logs.

Does this log analytics pipeline require specific ports for its setup manifest workflow?

The log analytics pipeline requires defined data flows on port 1002 and 443 to execute its setup manifest workflow, ensuring proper communication between the collector, parser, alerter, and dashboard agents.