Observability integration with Spinal
Project description
sp-obs
SP-OBS is Spinal's cost tracking library built on top of OpenTelemetry. It works by automatically instrumenting HTTP libraries (httpx, requests, aiohttp) and gRPC calls, while attaching a processor to existing OpenTelemetry setups. This dual approach allows it to integrate seamlessly with existing observability frameworks while selectively forwarding AI/LLM operations and billing events to Spinal's platform.
Features
- Seamlessly integrates with existing OpenTelemetry setups
- Works with Logfire, vanilla OpenTelemetry, or any OTEL-compatible framework
- Automatic instrumentation of httpx, requests, aiohttp libraries and gRPC calls
- Adds user and workflow context to spans for better tracking
- Selective span processing - only sends relevant AI/billing spans
- Built-in data scrubbing for sensitive information
Installation
pip install sp-obs
Quick Start
import sp_obs
# Configure with your API key
sp_obs.configure(api_key="your-api-key")
# That's it! AI calls are now tracked automatically
Integration with Other Observability Tools
IMPORTANT: When using sp-obs alongside other OpenTelemetry providers (Logfire, Langwatch, Langsmith, Langfuse, etc.), you MUST set set_global_tracer=False to prevent tracer conflicts.
By default, sp-obs sets itself as the global tracer provider. When another OTEL library is already managing tracing, both libraries attempting to set the global tracer will cause conflicts.
Using with Langwatch/Langsmith/Langfuse
import langwatch
# Set up your primary observability tool first
langwatch.setup(api_key="your-langwatch-key")
# Configure sp-obs with set_global_tracer=False
sp_obs.configure(
api_key="your-spinal-key",
set_global_tracer=False
)
Using with Logfire
import logfire
import sp_obs
# Set up Logfire first
logfire.configure()
# Configure sp-obs with set_global_tracer=False
sp_obs.configure(
api_key="your-spinal-key",
set_global_tracer=False
)
Note: sp-obs will still capture and forward AI/LLM spans to Spinal even with set_global_tracer=False. It works by attaching its processor to the existing tracer provider.
Adding Context
Use tags to add business context to your AI operations:
# Context manager (recommended)
with sp_obs.tag(user_id="user-123", workflow_id="chat-session"):
# All AI calls here will be tagged
response = openai_client.chat.completions.create(...)
# Or set tags globally
sp_obs.tag(user_id="user-123", workflow_id="chat-session")
Supported Providers
LLMs: OpenAI, Anthropic, Perplexity Text-to-Speech: ElevenLabs Speech-to-Text: Deepgram APIs & Tools: SerpAPI, ScrapingBee, Firecrawl
Billing Events
Track custom billing events within a tagged context:
with sp_obs.tag(user_id="user-123", workflow_id="checkout"):
sp_obs.add_billing_event(
success=True,
amount=99.99,
currency="USD"
)
Environment Variables
SPINAL_API_KEY- Your API keySPINAL_TRACING_ENDPOINT- Custom endpoint (default: https://cloud.withspinal.com)
Advanced Configuration
Batch Processing
Control how spans are batched and exported to optimize for your application's needs:
sp_obs.configure(
api_key="your-api-key",
max_queue_size=2048, # Max buffered spans before dropping
max_export_batch_size=512, # Spans per batch
schedule_delay_millis=5000, # Export interval (ms)
export_timeout_millis=30000 # Export timeout (ms)
)
Parameter Guide:
-
max_queue_size(default: 2048)- Controls memory usage
- Increase for high-volume applications (10k+ spans/min) to prevent drops during traffic spikes
- Decrease for resource-constrained environments to limit memory footprint
- Performance impact: Higher values = more memory but fewer outgoing network calls
-
max_export_batch_size(default: 512)- Balances network efficiency vs. latency
- Increase (up to 2048) for high-throughput applications to reduce network overhead
- Decrease (to 128-256) for low-latency requirements to export spans more frequently
- Performance impact: Larger batches = better network efficiency but slightly higher latency
-
schedule_delay_millis(default: 5000ms)- How often to export spans, regardless of batch size
- Decrease (to 1000-2000ms) when you need near real-time visibility
- Increase (to 10000-30000ms) to reduce API calls and network overhead
- Performance impact: Lower values = fresher data but more API calls and network usage
-
export_timeout_millis(default: 30000ms)- Maximum time to wait for export to complete before failing
- Increase for unreliable networks or when exporting large batches
- Decrease if you prefer to drop spans rather than block on slow exports
- Performance impact: Only matters when network is slow; higher values prevent timeouts
Recommended Configurations:
# High-volume production (10k+ spans/min)
sp_obs.configure(max_queue_size=4096, max_export_batch_size=1024, schedule_delay_millis=3000)
# Low-latency requirements (real-time dashboards)
sp_obs.configure(max_queue_size=1024, max_export_batch_size=128, schedule_delay_millis=1000)
# Resource-constrained (serverless, edge)
sp_obs.configure(max_queue_size=512, max_export_batch_size=256, schedule_delay_millis=10000)
Data Scrubbing
Automatically redact sensitive information from spans:
from sp_obs import DefaultScrubber, NoOpScrubber
# Use default scrubber (removes tokens, keys, passwords)
sp_obs.configure(
api_key="your-api-key",
scrubber=DefaultScrubber()
)
# Disable scrubbing
sp_obs.configure(
api_key="your-api-key",
scrubber=NoOpScrubber()
)
# Custom scrubber
class CustomScrubber:
def scrub_attributes(self, attributes: dict) -> dict:
# Your scrubbing logic
return attributes
sp_obs.configure(
api_key="your-api-key",
scrubber=CustomScrubber()
)
Additional Options
sp_obs.configure(
api_key="your-api-key",
endpoint="https://custom.endpoint.com", # Custom endpoint
headers={"X-Custom": "header"}, # Additional headers
timeout=10, # Request timeout (seconds)
set_global_tracer=False # See "Integration with Other Observability Tools"
)
License
MIT
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file sp_obs-0.5.3.tar.gz.
File metadata
- Download URL: sp_obs-0.5.3.tar.gz
- Upload date:
- Size: 128.1 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
c61c09bb918e7de1e2b6b2f8ea6958ffa78e41e38a9304dd48844e508a0c30c1
|
|
| MD5 |
ee096ff257160186eac9dcb26a4fb46b
|
|
| BLAKE2b-256 |
716dfd3d50aa62631fdfa9ce94a79054982573026249191808ee7b8d2de74ec7
|
Provenance
The following attestation bundles were made for sp_obs-0.5.3.tar.gz:
Publisher:
publish-to-pypi.yml on withspinal/sp-obs
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
sp_obs-0.5.3.tar.gz -
Subject digest:
c61c09bb918e7de1e2b6b2f8ea6958ffa78e41e38a9304dd48844e508a0c30c1 - Sigstore transparency entry: 662584214
- Sigstore integration time:
-
Permalink:
withspinal/sp-obs@34bc62948bf88fd590a1ee68192f914797eb5c90 -
Branch / Tag:
refs/tags/v0.5.3 - Owner: https://github.com/withspinal
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish-to-pypi.yml@34bc62948bf88fd590a1ee68192f914797eb5c90 -
Trigger Event:
push
-
Statement type:
File details
Details for the file sp_obs-0.5.3-py3-none-any.whl.
File metadata
- Download URL: sp_obs-0.5.3-py3-none-any.whl
- Upload date:
- Size: 41.6 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
602244597a18eab3264bfbf54cae06492b60a7879a030d6133f0b6ad97862829
|
|
| MD5 |
5f9741a6ec276bf814d603ace2091b15
|
|
| BLAKE2b-256 |
fe5e95d80e9597caa9143b196bcc7ec5b9cd748f9dab0254b0626b0254763094
|
Provenance
The following attestation bundles were made for sp_obs-0.5.3-py3-none-any.whl:
Publisher:
publish-to-pypi.yml on withspinal/sp-obs
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
sp_obs-0.5.3-py3-none-any.whl -
Subject digest:
602244597a18eab3264bfbf54cae06492b60a7879a030d6133f0b6ad97862829 - Sigstore transparency entry: 662584219
- Sigstore integration time:
-
Permalink:
withspinal/sp-obs@34bc62948bf88fd590a1ee68192f914797eb5c90 -
Branch / Tag:
refs/tags/v0.5.3 - Owner: https://github.com/withspinal
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish-to-pypi.yml@34bc62948bf88fd590a1ee68192f914797eb5c90 -
Trigger Event:
push
-
Statement type: