tinysocs-run-and-operate

Installs, runs, and operates TinySocs SIEM services on Windows hosts.

Updated Oct 12, 2025
One-click install
npx skills add https://github.com/lukefitzg/tinysocs --skill tinysocs-run-and-operate-lukefitzg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tinysocs-run-and-operate
Source: https://github.com/lukefitzg/tinysocs/tree/main/.claude/skills/tinysocs-run-and-operate
Command: npx skills add https://github.com/lukefitzg/tinysocs --skill tinysocs-run-and-operate-lukefitzg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operating a self-hosted TinySocs SIEM on a real Windows host involves a maze of installer internals, NSSM-wrapped services, ProgramData paths, scheduled tasks, and retention policies — this Skill gives you verified, line-cited ground truth so you can install, run, and troubleshoot a pilot or customer host without guessing. ## Core Features & Use Cases - Installer and service operations: Explains the Inno Setup flow (Quickstart.iss), the TinySocs.Installer.psm1 module with 210 functions, and the NSSM-wrapped services (TinySocsOpenSearch, TinySocsAgent, TinySocsNode, TinySocsAssistant) including ports, dependencies, and restart behavior. - Filesystem and log navigation: Maps the full C:\ProgramData\TinySocs layout, every log file location, scheduled tasks, ISM retention policies, and the 60-second rule hot-reload behavior. - Upgrade, uninstall, and VM deployment: Documents upgrade backup behavior, the remove_on_uninstall.flag data-wipe opt-in, and the two-script deploy-bundle pipeline for hot-swapping an agent and rules.yml on a validation VM. - Use Case: You are standing up a pilot TinySocs host and the dashboard is not responding after install — use this Skill to learn that OpenSearch cold start can take up to 300 seconds on port 9201 and where to find the postinstall logs before assuming failure. ## Quick Start Ask the assistant to walk you through installing TinySocs on a Windows VM and verifying which services and scheduled tasks should be running afterward.

Frequently Asked Questions about tinysocs-run-and-operate

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

FAQPage Schema
How do I install TinySocs on a Windows host?▼

Run TinySocs-Setup.exe as Administrator and pick the Hub role; the Inno Setup wizard collects secrets, notification config, and dashboard bind mode, then a post-install chain registers OpenSearch, the agent, the assistant service, and dashboards. Verify with Test-TinySocsHealth in elevated PowerShell.

How do I update detection rules without restarting the TinySocs agent?▼

Edit C:\ProgramData\TinySocs\Collector\rules\rules.yml directly — the agent reloads rules every 60 seconds by default with no service restart. Confirm the reload by checking TinySocsAgent.out.log for a 'Detection engine updated with N rule' line.

Where are TinySocs log files located on Windows?▼

Agent logs live at C:\ProgramData\TinySocs\Collector\logs\TinySocsAgent.out.log and .err.log, assistant logs under Assistant\, OpenSearch logs under OpenSearch\logs\, and installer logs under logs\postinstall-powershell*.log. The uninstall log is at %TEMP%\tinysocs-uninstall.log.

Why is the TinySocs dashboard not responding right after install?▼

OpenSearch cold start can take up to 300 seconds on first boot, so an unresponsive port 9201 in the first few minutes is expected, not a failure. Wait, then check the OpenSearch logs and service status before troubleshooting further.

Does uninstalling TinySocs delete all my data and logs?▼

No — ProgramData (config, logs, ledger, queue) survives a genuine uninstall unless the file C:\ProgramData\TinySocs\remove_on_uninstall.flag exists. During upgrades the uninstaller detects the upgrade and always keeps ProgramData.

When should I not use this TinySocs operations skill?▼

Use other skills for health-check and smoke-test interpretation (tinysocs-diagnostics-and-tooling), building installer artifacts (tinysocs-build-and-env), change approval decisions (tinysocs-change-control), or debugging specific symptoms like agent silence or HMAC mismatches (tinysocs-debugging-playbook).