Skip to content

opensite-ai/opensite-skills / aws-observability

aws-observability

Unverified

Builds, 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.

FileKindSize
.aws-skill-metadataother18 B
SKILL.mdskill md28.3 KB
assets/cloudwatch/alarm-template.tsscript3.9 KB
assets/cloudwatch/otel-config.yamlconfig1.9 KB
references/cloudwatch-omni/agent-evaluation.mdmarkdown98.9 KB
references/cloudwatch-omni/alerts.mdmarkdown103.3 KB
references/cloudwatch-omni/concepts.mdmarkdown28.8 KB
references/cloudwatch-omni/context-graph.mdmarkdown29.2 KB
references/cloudwatch-omni/dashboards.mdmarkdown75.5 KB
references/cloudwatch-omni/programmatic-access.mdmarkdown8.6 KB
references/cloudwatch-omni/query/promql-metrics.mdmarkdown63.9 KB
references/cloudwatch-omni/query/sql-logs-traces.mdmarkdown43.0 KB
references/cloudwatch-omni/query/views.mdmarkdown12.7 KB
references/cloudwatch/alarms.mdmarkdown11.5 KB
references/cloudwatch/cloudtrail.mdmarkdown5.3 KB
references/cloudwatch/dashboards.mdmarkdown5.8 KB
references/cloudwatch/dynamic-instrumentation.mdmarkdown39.4 KB
references/cloudwatch/dynamic-instrumentation/breakpoint-creation.mdmarkdown16.3 KB
references/cloudwatch/dynamic-instrumentation/call-tree-and-directions.mdmarkdown5.7 KB
references/cloudwatch/dynamic-instrumentation/snapshot-parsing.mdmarkdown4.2 KB
references/cloudwatch/log-insights.mdmarkdown7.0 KB
references/cloudwatch/metrics.mdmarkdown7.4 KB
references/cloudwatch/synthetics.mdmarkdown6.5 KB
references/cloudwatch/tracing.mdmarkdown9.4 KB
references/cloudwatch/troubleshooting.mdmarkdown7.5 KB
scripts/cloudwatch-omni/capture_dataset_from_traces.pyscript19.2 KB
scripts/cloudwatch-omni/evaluate_traces.pyscript41.8 KB
scripts/cloudwatch-omni/test_evaluate_traces.pyscript12.0 KB
scripts/cloudwatch/di_app_signals_client.pyscript3.3 KB
scripts/cloudwatch/di_capture.pyscript8.5 KB
scripts/cloudwatch/di_constants.pyscript560 B
scripts/cloudwatch/di_crud_rendering.pyscript13.1 KB
scripts/cloudwatch/di_crud_tools.pyscript28.8 KB
scripts/cloudwatch/di_error_translation.pyscript5.6 KB
scripts/cloudwatch/di_formatting.pyscript992 B
scripts/cloudwatch/di_gateway.pyscript7.0 KB
scripts/cloudwatch/di_instrumentation.pyscript13.0 KB
scripts/cloudwatch/di_location.pyscript15.3 KB
scripts/cloudwatch/di_logs_client.pyscript4.2 KB
scripts/cloudwatch/di_region.pyscript2.0 KB
scripts/cloudwatch/di_result.pyscript2.0 KB
scripts/cloudwatch/di_session.pyscript2.0 KB
scripts/cloudwatch/di_snapshot_parsing.pyscript11.4 KB
scripts/cloudwatch/di_snapshot_queries.pyscript2.4 KB
scripts/cloudwatch/di_snapshot_rendering.pyscript12.5 KB
scripts/cloudwatch/di_snapshot_tools.pyscript12.0 KB
scripts/cloudwatch/di_snapshots.pyscript12.8 KB
scripts/cloudwatch/di_status_assessment.pyscript4.7 KB
scripts/cloudwatch/di_status_rendering.pyscript11.8 KB
scripts/cloudwatch/di_status_tools.pyscript13.0 KB
scripts/cloudwatch/di_validation.pyscript11.2 KB

scripts/cloudwatch/di_app_signals_client.py

View on GitHub
"""The application-signals boto3 client seam for the dynamic-instrumentation tools.

WHY THIS EXISTS (import-cycle removal)
  This module is the LEAF that owns ``get_application_signals_client()``. Previously the seam
  lived in ``di_instrumentation`` (the CLI entry point), so the operation modules reached it via
  ``di_crud_tools/di_status_tools -> di_gateway -> di_instrumentation`` — an import cycle back
  into the entry script, which forced every op module to be imported lazily. A client seam is a
  leaf concern (it depends only on ``di_session``/``di_region``), so it belongs in its own leaf
  module. With it here, ``di_gateway`` imports DOWN into this module and nothing imports back
  into ``di_instrumentation``: the cycle is gone. This mirrors how ``di_session`` / ``di_region``
  already factor out the shared client-construction policy.

  ``boto3``/``botocore`` are imported lazily (inside ``di_session.build_client``), so importing
  this module never requires boto3 — which is what lets the build env (which omits boto3) import
  ``di_instrumentation`` for the ``APPLICATION_SIGNALS_API_VERSION`` constant. (Running
  ``--print-contract`` is a separate matter: it resolves the op functions and so does pull in
  ``botocore`` via the op modules — only the bare module import is boto3-free.)
"""

# The application-signals instrumentation API version the operations were authored against; the
# public SDK serves it. Surfaced (informationally) by di_instrumentation --print-contract.
APPLICATION_SIGNALS_API_VERSION = "2024-04-15"
# Minimum boto3/botocore that ships the DI operations in the public model. Surfaced only in the
# fail-fast upgrade message — the actual gate is operation presence (see _MIN_DI_OPERATION).
MIN_BOTO3_VERSION = "1.43.35"
# Canary operation: if the installed SDK's application-signals model lacks this, the whole DI
# surface is missing and we should tell the caller to upgrade rather than fail mid-operation.
_MIN_DI_OPERATION = "CreateInstrumentationConfiguration"

_application_signals_client = None


def get_application_signals_client():
    """Return a lazily-built `application-signals` client from the installed boto3.

    The `di_gateway` module imports this symbol. Region resolves from --region/AWS_REGION/
    AWS_DEFAULT_REGION (default us-east-1); AWS_PROFILE is honored for credentials only. The DI
    operations ship in the public SDK as of boto3 1.43.35 (MIN_BOTO3_VERSION), so this is an
    ordinary client — no bundled model, no data-loader manipulation. If the installed SDK
    predates the DI operations we raise a clear upgrade error instead of letting an
    `AttributeError` surface deep inside an operation.
    """
    global _application_signals_client
    if _application_signals_client is not None:
        return _application_signals_client

    from di_session import build_client

    client = build_client("application-signals")
    if _MIN_DI_OPERATION not in client.meta.service_model.operation_names:
        raise RuntimeError(
            "The installed AWS SDK does not expose the Dynamic Instrumentation operations "
            f"(missing {_MIN_DI_OPERATION!r} on the application-signals model). Upgrade to "
            f"boto3/botocore >= {MIN_BOTO3_VERSION}: pip install --upgrade "
            f"'boto3>={MIN_BOTO3_VERSION}'."
        )
    _application_signals_client = client
    return _application_signals_client
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall