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.

Drive new-customer setup checklist — welcome email, kickoff scheduling, shared Notion workspace, Slack notification, milestone tracking. Event-triggered on Stripe checkout success or CRM Stage="Closed Won".

Literature survey and SOTA tracking specialist. Use when the user asks to talk to Sova, requests the research tracker, or needs literature review, citation mapping, and paper analysis.

Track and visualize ML training experiments with Trackio, including logging metrics, firing alerts, and retrieving data via CLI. Supports real-time dashboards, webhook alerts, and HF Space syncing.

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.

Monitor service level agreements and generate compliance reports with breach alerts

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

Detect SSO and OAuth token replay and SaaS lateral movement using identity telemetry from Microsoft Entra ID and Okta.

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

`analysis-agent`/`task-agent`/`review-agent`: primary-Skill-selected for logs, metrics, traces, alerts, SLI/SLO, or diagnostics; never task owner; skip without signal impact.

Configure, deploy, and manage Senpi Trading Runtime (OpenClaw plugin @senpi-ai/runtime) for automated on-chain position tracking with DSL trailing stop-loss protection. Use when a user needs to create or modify runtime YAML files, configure DSL (Dynamic Stop-Loss) exit engine parameters (phases, tiers, time-based cuts), set up the position_tracker scanner to monitor a wallet's positions on Hyperliquid, install/list/delete runtimes via CLI, or inspect DSL-tracked positions. The runtime does NOT create strategy wallets; create/get the strategy wallet via Senpi MCP first, then link that existing wallet in runtime YAML. Triggers on mentions of senpi, Senpi runtime, DSL exit, stop-loss tiers, position tracker, trailing stop, openclaw senpi, dsl_preset, or strategy YAML configuration."

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

Track ML experiments with automatic logging, visualize training in real-time, optimize hyperparameters with sweeps, and manage model registry with W&B.

Provides real-time Chicago CTA transit data including L train arrivals, bus predictions, service alerts, and route information using official CTA APIs.

Monitor a live model for data quality, input and prediction drift, performance decay, and fire retraining triggers.

Tracks the dates of skills in the repository, with details maintained in a separate document.

Track Slack communities, Discord servers, Facebook groups, and forums for buying signals and engagement opportunities

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.

Debug agent execution by querying trace and metric tables, analyzing tool calls, durations, errors, and performance trends.

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.

Tracks RSS/Atom feeds and blogs using blogwatcher-cli, with feed discovery, HTML scraping fallback, OPML import, and read/unread article management.

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

Defines service level indicators, objectives, and agreements, calculates error budgets, and sets up Prometheus and Grafana monitoring for SLO compliance.

Import recorded driving sensor data (GPS, camera, lidar, actor tracks, lanes) into scenariobuilder.* objects (GPSData, CameraData, LidarData, ActorTrackData, Trajectory, laneData) and run preprocessing — synchronize, offset correction, crop, normalizeTimestamps, convertTimestamps. Also: compute actor tracks from lidar when no annotations exist, attach camera/lidar mounting + intrinsics, export to MAT/workspace/timetable/script. Use for raw driving dataset files (KITTI, nuScenes, Waymo, Pandaset, ROS/ROS2 bags, .mat, .csv, .mp4) or driving/vehicle/sensor logs that need wrapping. drivingLogAnalyzer (DLA) is OPT-IN ONLY — invoke only on explicit user request ('DLA', 'open in DLA', 'inspect/explore/analyze the recording') or reported sensor problem (sync drift, timestamp mismatch, overlay misalignment). NEVER auto-launch DLA after wrapping (Rule 0). For 'build scenario / export to RoadRunner / drivingScenario / OpenSCENARIO / Unreal / simulate', hand off to matlab-use-scenario-builder.

Slack archive: search, sync freshness, threads/DMs, SQL counts, and Slacrawl repo work.

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

Design a lead routing and SLA model someone can actually implement. The assignment rules, the round-robin or account-based logic, the SLA timers, and the fallbacks when a rep is out or a lead has no owner. Built for B2B RevOps teams, customizable to your CRM and your team shape. Trigger on "design lead routing", "who should get this lead", "build our SLA", "round robin rules", "leads are falling through", or any routing diagnostic.

Audit server-side paid-media measurement, including tag management, conversion APIs, event taxonomy, deduplication, consent, hashing, data quality, and observability.