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_delete_instrumentation_configurations operation
        response = await application_signals.batch_delete_instrumentation_configurations()
        print(response["deleted_count"])

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 get_instrumentation_configuration_status
        async for item in application_signals.iter_get_instrumentation_configuration_status():
            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_delete_instrumentation_configurations()
        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_delete_instrumentation_configurations()

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

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

Metadata

Release files for capo-application-signals 0.8.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.8.0
File Size Uploaded Provenance
capo_application_signals-0.8.0.tar.gz 165.2 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 520.5 kB

Release files / capo_application_signals-0.8.0.tar.gz

Download URL capo_application_signals-0.8.0.tar.gz
Size 165.2 kB
Tags Source
SHA-256 checksum
How to use checksums
dfe6f8c1d345b6496d9e40c520c47a7d927cf3118b2f4b5e9174af974336e1e2
BLAKE2b-256 checksum
How to use checksums
92f548c7f4ac77586f36c7f6b54b0cd9caf1c5734786c77b9ddfb5023a621914
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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.8.0-py3-none-any.whl

Download URL capo_application_signals-0.8.0-py3-none-any.whl
Size 355.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e62a7f85120c46f266e15ac213de9a5e4517218f6ace919b862daabf0cbddd42
BLAKE2b-256 checksum
How to use checksums
e315892866d0357671041306a64177dae7ad34d1e7f43b0e1a91a0c711858f92
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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.8.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