Skip to main content

Getting Started

Installation

pip install capo-networkmonitor

Usage

from capo_networkmonitor import AsyncNetworkMonitorClient


async def main():
    async with AsyncNetworkMonitorClient() as network_monitor:
        # Example: call the list_tags_for_resource operation
        response = await network_monitor.list_tags_for_resource()
        print(response["tags"])

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_networkmonitor import AsyncNetworkMonitorClient


async def main():
    async with AsyncNetworkMonitorClient() as network_monitor:
        # Example: paginate over list_monitors
        async for item in network_monitor.iter_list_monitors():
            print(item)

Error Handling

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

from capo_networkmonitor import AsyncNetworkMonitorClient
from capo_networkmonitor.error import AccessDeniedException


async def main():
    async with AsyncNetworkMonitorClient() as network_monitor:
        try:
            await network_monitor.list_tags_for_resource()
        except AccessDeniedException 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_networkmonitor import AsyncNetworkMonitorClient


async def main():
    async with AsyncNetworkMonitorClient() as network_monitor:
        # Default: 3 attempts for every operation
        response = await network_monitor.list_tags_for_resource()

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

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

Metadata

Release files for capo-networkmonitor 0.7.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-networkmonitor 0.7.0
File Size Uploaded Provenance
capo_networkmonitor-0.7.0.tar.gz 81.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-networkmonitor 0.7.0
File Interpreter ABI Platform
capo_networkmonitor-0.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 211.8 kB

Release files / capo_networkmonitor-0.7.0.tar.gz

Download URL capo_networkmonitor-0.7.0.tar.gz
Size 81.2 kB
Tags Source
SHA-256 checksum
How to use checksums
e9ed0443220aeb456035177def6cb6c618b1cdb2806b33b0eac9f0af4db5482d
BLAKE2b-256 checksum
How to use checksums
8a6aaa73cce535904bf27d2a73f8ba1660cf1bb1142fcb70f3a77e8b8f446ab1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","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_networkmonitor-0.7.0-py3-none-any.whl

Download URL capo_networkmonitor-0.7.0-py3-none-any.whl
Size 130.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7cc2e4836d8c7760a7d0edad07dafcf09e58e4577e018bf79b2a495c13073911
BLAKE2b-256 checksum
How to use checksums
8bea764c3347c447ebedcc79c5167468999a11d4e40076f3f5600ee2adaca754
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","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-networkmonitor 0.7.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