Skip to main content

Raindrop observability integration for AWS Bedrock

Project description

raindrop-bedrock

PyPI version Python License: MIT

Raindrop observability integration for AWS Bedrock (Python). Automatically captures converse() and invoke_model() calls by wrapping the boto3 bedrock-runtime client.

Installation

pip install raindrop-bedrock

For async support with aioboto3:

pip install raindrop-bedrock[async]

Quick Start

import boto3
from raindrop_bedrock import RaindropBedrock

rb = RaindropBedrock(api_key="your-write-key", user_id="user-123")

client = boto3.client("bedrock-runtime", region_name="us-east-1")
rb.wrap(client)

response = client.converse(
    modelId="anthropic.claude-3-5-sonnet-20241022-v2:0",
    messages=[{"role": "user", "content": [{"text": "Hello!"}]}],
)

rb.flush()

Projects

Route events to a specific project by passing its slug as project_id:

rb = RaindropBedrock(
    api_key="your-write-key",
    project_id="support-prod",
)

project_id sets the X-Raindrop-Project-Id header on every event. Omit it (or pass "default") to use your org's default Production project, which is the existing behavior. The same option is accepted by the create_raindrop_bedrock(...) factory. Invalid slugs are ignored with a warning and no header is sent.

Debug Mode

Enable verbose logging with the debug flag:

rb = RaindropBedrock(api_key="your-write-key", user_id="user-123", debug=True)

Async Usage

import aioboto3
from raindrop_bedrock import RaindropBedrock

rb = RaindropBedrock(api_key="rk_...", user_id="user-123")

session = aioboto3.Session()
async with session.client("bedrock-runtime", region_name="us-east-1") as client:
    rb.async_wrap(client)
    response = await client.converse(
        modelId="anthropic.claude-3-5-sonnet-20241022-v2:0",
        messages=[{"role": "user", "content": [{"text": "Hello!"}]}],
    )

rb.flush()

identify()

Associate a user with optional traits:

rb.identify(user_id="user-123", traits={"plan": "pro", "company": "Acme"})

track_signal()

Track feedback, edits, or custom signals:

rb.track_signal(
    event_id="evt_abc123",
    name="thumbs_up",
    signal_type="feedback",
    sentiment="POSITIVE",
    comment="Great answer!",
)

flush() / shutdown()

Always call flush() before your process exits to ensure all telemetry is shipped:

rb.flush()      # flush pending data
rb.shutdown()   # flush + release resources

Legacy Factory Function

The create_raindrop_bedrock() factory function is still supported for backwards compatibility:

from raindrop_bedrock import create_raindrop_bedrock

raindrop = create_raindrop_bedrock(api_key="your-write-key", user_id="user-123")
client = boto3.client("bedrock-runtime", region_name="us-east-1")
raindrop.wrap(client)

What Gets Captured

Method Captured Data
converse() Input messages, output text, model ID, token usage (inputTokens/outputTokens), stop reason (stopReason), cached tokens (cacheReadInputTokenCount, cacheWriteInputTokenCount), conversation ID
invoke_model() Raw request/response bodies, model ID, token usage (Claude, Titan, and Llama formats), stop reason (Claude: stop_reason, Llama: stop_reason), cached tokens (Claude: cache_read_input_tokens)
Errors Error type and message are captured in event properties, then the exception is re-raised

Captured Properties

Property Key Source Description
ai.usage.prompt_tokens Both APIs Input/prompt token count
ai.usage.completion_tokens Both APIs Output/completion token count
ai.usage.cached_tokens Converse: cacheReadInputTokenCount; Claude InvokeModel: cache_read_input_tokens Tokens read from cache
ai.usage.cache_write_tokens Converse: cacheWriteInputTokenCount Tokens written to cache
bedrock.finish_reason Converse: stopReason; InvokeModel: varies by model Why the model stopped generating

API Reference

RaindropBedrock(api_key=None, user_id=None, convo_id=None, project_id=None, tracing_enabled=True, bypass_otel_for_tools=True, disable_auto_instrument=True, debug=False)

Parameter Type Default Description
api_key str | None None Raindrop API key. Warns if not provided.
user_id str | None None Default user ID for events (falls back to "unknown")
convo_id str | None None Group events into a conversation
project_id str | None None Route events to a specific project (slug); omit for the default Production project
tracing_enabled bool True Enable Raindrop tracing
bypass_otel_for_tools bool True Bypass OpenTelemetry for tool-level instrumentation
disable_auto_instrument bool True Library auto-instrumentation is opt-in (see below)
debug bool False Enable verbose DEBUG-level logging

Library auto-instrumentation is opt-in

As of 0.0.4, disable_auto_instrument defaults to True: the integration no longer lets Traceloop monkey-patch every LLM client library it recognizes in your process (botocore client creation, OpenAI, Anthropic, etc.). The wrapper captures input/output, token usage, model name, and stop reason directly from the wrapped boto3 client's responses, so no library patching is needed for full dashboards.

If you specifically want LLM-call-level spans from library instrumentation and have verified compatibility in your environment, opt back in with disable_auto_instrument=False.

Methods

Method Description
wrap(client) Instrument a sync boto3 bedrock-runtime client
async_wrap(client) Instrument an async aioboto3 bedrock-runtime client
identify(user_id, traits=None) Identify a user with optional traits
track_signal(event_id, name, ...) Track a signal event
flush() Flush pending events
shutdown() Flush and shut down

Testing

cd packages/bedrock-python
pip install -e ".[async]"
pip install pytest
python -m pytest tests/ -v

Known Limitations

  • InvokeModel body replacement: After consuming the response body stream, it's replaced with a BytesIO object. Callers using StreamingBody.read() will get the same bytes, but the original StreamingBody API is not preserved.
  • Async support requires the [async] extra (aioboto3>=12.0.0).

Full Documentation

docs.raindrop.ai/integrations/bedrock

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

raindrop_bedrock-0.0.7.tar.gz (27.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

raindrop_bedrock-0.0.7-py3-none-any.whl (11.9 kB view details)

Uploaded Python 3

File details

Details for the file raindrop_bedrock-0.0.7.tar.gz.

File metadata

  • Download URL: raindrop_bedrock-0.0.7.tar.gz
  • Upload date:
  • Size: 27.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for raindrop_bedrock-0.0.7.tar.gz
Algorithm Hash digest
SHA256 dd3515b40d35b3963eb4fe089565640634e5294cb2fbebc126c54079fcbd00a3
MD5 81143fb8e1b7d6f3b463e84f04cc6360
BLAKE2b-256 c1d2e6306dd7923397d62e736cbf033aad49434689df65c7da357ff01dc0872b

See more details on using hashes here.

File details

Details for the file raindrop_bedrock-0.0.7-py3-none-any.whl.

File metadata

File hashes

Hashes for raindrop_bedrock-0.0.7-py3-none-any.whl
Algorithm Hash digest
SHA256 261348582350ac21be189b7614bae1be3ce9371186544b5048aedb96f97b4a5b
MD5 b1185b2d6908ea52d4977ae8c271f130
BLAKE2b-256 d60690ccdee38f69fd4cc91b7b58a51e436d94fb4d7f2ae7192b54eb26f8ea02

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page