opensite-ai/opensite-skills / aws-observability
aws-observability
UnverifiedBuilds, configures, debugs, and optimizes AWS observability - operator-symptom questions and detecting Omni vs classic CloudWatch. CloudWatch on an already-reporting service: Log Insights, metric/composite/anomaly alarms, custom metrics/EMF, dashboards, X-Ray/ADOT tracing, canaries, CloudTrail, Dynamic Instrumentation (live breakpoints/snapshots), the Application Signals service map, and fleet health views. CloudWatch Omni on an existing Space: SQL over logs and traces, PromQL over metrics, Omni dashboards, Omni alerts, context graph for root cause, programmatic/IaC access (API/SDK/CLI/CloudFormation), driving Omni from a coding agent or skills, and evaluating AI agent quality from traces - on-demand and online scoring of live traffic, readback, custom evaluators. For first-time setup - creating an Omni Space, granting access, ingestion, or ADOT instrumentation for Application Signals (ServiceEvents, CI/CD metadata) or Omni - use setting-up-cloudwatch-observability. Not for app logging or threat detection.
scripts/cloudwatch/di_result.py
View on GitHub"""The structured result returned by instrumentation-config / status operations.
WHY THIS EXISTS
The CRUD and status operation functions (in ``di_crud_tools`` / ``di_status_tools``)
return a human-readable string for both success and failure and never raise. That
text is what the agent reads. But the entry script (``di_instrumentation.py``) also
needs to derive a process exit code from each operation, and historically it did so
by *string-matching* the rendered prose ("Failed to ...", "DELETE ERRORS:", etc.) —
wording owned by several other modules. Rewording any renderer could silently flip a
real failure to exit 0.
``OpResult`` separates the two concerns that the bare string conflated:
* ``ok`` — the STATUS channel. Drives the process exit code (``0`` if ``ok`` else
``1``). Set by each operation at the point where success vs. failure is
actually known (the ``except GatewayError`` site, the early ``ERROR:``
return, the success render).
* ``text`` — the PRESENTATION channel. The rendered human string, unchanged from
before; the entry script prints it verbatim.
``ok`` is about whether the *operation* succeeded, NOT about the AWS instrumentation
lifecycle state. A ``check-status`` call that successfully reports a breakpoint in the
ERROR state is ``OpResult(ok=True, ...)`` — the query succeeded; the breakpoint's
status being ERROR is content in ``text``.
This module imports nothing so the entry script and both tools modules can import it
without any risk of an import cycle.
"""
from dataclasses import dataclass
@dataclass(frozen=True)
class OpResult:
"""The (status, presentation) pair an operation returns.
Attributes:
ok: True when the operation succeeded; False for any input/validation/AWS
failure. Maps to exit code ``0``/``1`` in the entry script.
text: The rendered human-readable message the agent reads (printed verbatim).
"""
ok: bool
text: str
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |