Results for “sla-tracking”

Design SLA monitoring with alerts, dashboards, and reporting. TRIGGERS - Use when user needs help with sla-monitor related tasks.

Design SLA monitoring with alerts, dashboards, and reporting. TRIGGERS - Use when user needs help with sla-monitor related tasks.

Track ML experiments with open-source run logging, local or self-hosted dashboards, and media visualization using SwanLab.

Provides guidance for experiment tracking with SwanLab. Use when you need open-source run tracking, local or self-hosted dashboards, and lightweight media logging for ML workflows.

Build automated alerting for vulnerability remediation SLA breaches with severity-based timelines, escalation workflows, and compliance reporting dashboards.

Monitors SLA compliance with real-time dashboards, breach alerts, and performance reporting

Detect adversary lateral movement across networks using Splunk SPL queries against Windows authentication logs, SMB traffic, and remote service abuse.

ORCA v2.0 — Gen-2 Striker with momentum event quality confirmation. FIRST_JUMP detection enhanced with Tier 2 momentum events and TCS trader quality tags. Stalker permanently removed. DSL exit managed by plugin runtime via runtime.yaml.

Engineering observability and reliability: SLO/SLI design, distributed tracing, alerting, dashboards, capacity planning, toil automation, reliability review. Use for instrumentation or SLO definition.

Detect APT lateral movement by chaining Windows authentication events, process execution telemetry, and network connection logs across hosts using Splunk SPL and Sigma rule format.

Detects lateral movement techniques including Pass-the-Hash, PsExec, WMI execution, RDP pivoting, and SMB-based spreading using SIEM correlation of Windows event logs, network flow data, and endpoint telemetry mapped to MITRE ATT&CK Lateral Movement (TA0008) techniques.

Progress Tracking

Java logging with SLF4J facade, Logback, and Log4j2 implementations. Covers configuration, log levels, structured logging, async logging, and production best practices for Spring Boot applications. USE WHEN: user mentions "java logging", "spring boot logging", "slf4j setup", asks about "how to log in java", "logback vs log4j2", "java logging best practices" DO NOT USE FOR: Node.js logging - use `nodejs-logging` instead, Python logging - use `python-logging`, Kotlin-specific logging - similar but has nuances

Trigger: structured logging, tracing, telemetry, SLI metrics, SLO alerts, log formats. Scope: Performance metrics, error tracing, production telemetry. Boundary: Excludes client behavioral product funnels.

Dynamic instrumentation via Frida - attach to or spawn a process, load a JS hook script, capture send() events into a lifecycle-managed run directory. Supports local, USB-attached, and remote frida-server targets.

Implements error tracking and crash reporting in Flutter apps using Sentry and Firebase Crashlytics, including automatic error capture, enriched context, breadcrumbs, and CI/CD integration for source maps and debug symbols.

Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>

Chicago CTA transit — real-time L train arrivals, bus predictions, service alerts, and route info. Use when the user asks about Chicago public transit, L train schedules, CTA bus times, service alerts, or nearby stops.

Set up and track KPI dashboards with targets, actuals, and trend analysis. TRIGGERS - Use when user wants to define KPIs, track metrics, or create a scorecard.

Create a strategy for selling to your first 100 customers using the minimalist entrepreneur playbook, with actionable steps for outreach, pricing, and tracking.