Skip to main content

Getting Started

Installation

pip install capo-application-signals

Usage

from capo_application_signals import AsyncApplicationSignalsClient


async def main():
    async with AsyncApplicationSignalsClient() as application_signals:
        # Example: call the batch_get_service_level_objective_budget_report operation
        response = await application_signals.batch_get_service_level_objective_budget_report()
        print(response["timestamp"])

Pagination

Some operations in this SDK support pagination. If the operation supports pagination it will have an iter_ prefixed method that returns an async iterator.

from capo_application_signals import AsyncApplicationSignalsClient


async def main():
    async with AsyncApplicationSignalsClient() as application_signals:
        # Example: paginate over list_entity_events
        async for item in application_signals.iter_list_entity_events():
            print(item)

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_application_signals import AsyncApplicationSignalsClient
from capo_application_signals.error import ThrottlingException


async def main():
    async with AsyncApplicationSignalsClient() as application_signals:
        try:
            await application_signals.batch_get_service_level_objective_budget_report()
        except ThrottlingException as e:
            print(f"Error: {e}")
            print(e.data)  # additional error data

Retrying

The SDK retries failed operations automatically. Retry behaviour follows the Smithy specification: errors are retried based on their is_retryable and is_throttling_error attributes. Throttling errors use a longer base delay. Network-level failures (connection errors and timeouts) are also retried. Non-retryable errors, such as client errors without the @retryable trait, are raised immediately without further attempts.

The number of attempts defaults to 3 and can be changed at the client level via retry_max_attempts, or per call via config_overrides.

from capo_application_signals import AsyncApplicationSignalsClient


async def main():
    async with AsyncApplicationSignalsClient() as application_signals:
        # Default: 3 attempts for every operation
        response = await application_signals.batch_get_service_level_objective_budget_report()

        # Override per operation
        response = await application_signals.batch_get_service_level_objective_budget_report(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await application_signals.batch_get_service_level_objective_budget_report(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-application-signals 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for capo-application-signals 0.1.0
File Size Uploaded Provenance
capo_application_signals-0.1.0.tar.gz 124.3 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-application-signals 0.1.0
File Interpreter ABI Platform
capo_application_signals-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 400.2 kB

Release files / capo_application_signals-0.1.0.tar.gz

Download URL capo_application_signals-0.1.0.tar.gz
Size 124.3 kB
Tags Source
SHA-256 checksum
How to use checksums
af4ef701cc9cf43651ee18282c84c7ecba80973026bb0d9a4a8ae4a44dfc8a5c
BLAKE2b-256 checksum
How to use checksums
021b432455de8534b0e22d715d3c71360ae92de60a194bc68a135f1d8244e693
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.14 {"installer":{"name":"uv","version":"0.12.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / capo_application_signals-0.1.0-py3-none-any.whl

Download URL capo_application_signals-0.1.0-py3-none-any.whl
Size 275.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a638834fbde93a791d0377527f61093c16295bfc1481b45a9abd6470e08a507c
BLAKE2b-256 checksum
How to use checksums
8262b479b93d0c4142934b91523ed9b86378830c423e3d4d398e9663a5658461
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.14 {"installer":{"name":"uv","version":"0.12.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for capo-application-signals 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page