Github action to collect metrics (CPU, memory, I/O, etc ...) from your workflows to help you debug and optimize your CI/CD pipeline

The Set Up Telemetry action provides deterministic OpenTelemetry trace IDs, job IDs and traceparent for GitHub Actions workflow telemetry.

Collects detailed system and environment telemetry from the GitHub Actions runner for workflow observability and diagnostics

Produces Telemetry data for GitHub Actions

No description available

No description available

No description available

This action will export GitHub Workflow telemetry data using OTLP to a configurable endpoint.

Workflow-agnostic GitHub Actions ingestion skeleton for collecting workflow run, job, and step telemetry across multiple repositories and storing in GCP Cloud SQL

Autonomous AI-driven OS Commander & Companion. Bridges system telemetry with AI action execution, security forensics, and automated web workflows.

An example of a GitHub Workflow that uses the Coveralls GitHub action to send test telemetry data to coveralls.io

Integrated LimaCharlie (EDR) with Tines (SOAR) to build an automated security workflow that detects threats, triggers response actions, and delivers alerts through Slack and Email using real-time telemetry and API-based automation.

Built a cloud-based Active Directory domain, then implemented a detection and response environment with Splunk (SIEM) and Shuffle (SOAR) to detect unauthorized logins and automate response actions, using real-time log telemetry and API-driven workflows.

It’s a Reactive SIEM FYP that proves an end-to-end workflow where endpoint telemetry (IDS/IPS, honeypot, FIM) is normalized and correlated, then turned into permissioned, auditable response actions (RBAC‑guarded), so detections can drive real containment steps—not just reporting.