Skip to main content

vibex.sh Python SDK - Fail-safe logging handler for vibex.sh

Project description

vibex.sh Python SDK

Fail-safe logging handler for sending logs to vibex.sh.

Features

  • Fail-Safe: Silently disables if configuration is missing or invalid
  • Kill Switch: Permanently disables on 401/403 errors (expired/invalid tokens)
  • Easy Integration: Drop-in Python logging handler
  • Zero Dependencies (except requests)

Installation

pip install vibex_sh

Quick Start

  1. Set environment variables:
export VIBEX_TOKEN=vb_live_your_token_here
export VIBEX_SESSION_ID=my-production-app
  1. Use in your Python application:
import logging
import json
from vibex_sh import VibexHandler

# Get your logger
logger = logging.getLogger('my_app')

# Add Vibex handler
vibex_handler = VibexHandler()
logger.addHandler(vibex_handler)

# Send JSON logs (only JSON logs are sent to Vibex)
logger.info(json.dumps({'cpu': 45, 'memory': 78, 'status': 'healthy'}))
logger.info(json.dumps({'error': 'connection_failed', 'retry_count': 3}))

Configuration

The SDK reads configuration from environment variables:

  • VIBEX_TOKEN (required): Your Vibex API token
  • VIBEX_SESSION_ID (required): Your session ID
  • VIBEX_API_URL (optional): API endpoint (default: https://vibex.sh/api/v1/ingest)

Fail-Safe Behavior

The SDK is designed to be fail-safe:

  1. Missing Config: If VIBEX_TOKEN or VIBEX_SESSION_ID is missing, the handler silently disables itself
  2. Invalid Token: On 401/403 responses, the handler permanently disables for the process lifetime
  3. Network Errors: All network errors are silently handled - your application continues normally
  4. Rate Limits: On 429 (rate limit), logs are dropped but the handler remains enabled. Logs are still written to console by default (passthrough_console=True)

Console Passthrough Options

By default, logs are forwarded to Vibex and also written to stderr (console), ensuring you can always see your logs locally while they're sent to Vibex.

passthrough_console (default: True)

When enabled (default), logs are always written to stderr in addition to being sent to Vibex. This provides visibility into your logs while forwarding them to Vibex.

# Default behavior - logs written to console and sent to Vibex
vibex_handler = VibexHandler()  # passthrough_console=True by default
logger.addHandler(vibex_handler)

# To disable console output (logs only sent to Vibex)
vibex_handler = VibexHandler(passthrough_console=False)
logger.addHandler(vibex_handler)

passthrough_on_failure (default: False)

When enabled, logs are written to stderr when sending to Vibex fails (rate limits, network errors, etc.). This is useful as an additional safety net, but with passthrough_console=True by default, it's typically not needed.

# Write logs to console only when sending fails
vibex_handler = VibexHandler(passthrough_console=False, passthrough_on_failure=True)
logger.addHandler(vibex_handler)

Important: Non-JSON logs are still discarded (only JSON-formatted logs are processed).

Important: JSON-Only Logging

Only JSON-formatted logs are sent to Vibex. Non-JSON logs are automatically discarded. Always stringify your log data:

import json

# ✅ Good - JSON logs are sent
logger.info(json.dumps({'cpu': 45, 'memory': 78}))

# ❌ Bad - Non-JSON logs are discarded
logger.info('Application started')
logger.info('High memory usage: 85%')

Advanced Usage

Direct Client Usage

from vibex_sh import VibexClient, VibexConfig

config = VibexConfig()
client = VibexClient(config)

# Send custom log
client.send_log('json', {'cpu': 45, 'memory': 78})

Check if Enabled

handler = VibexHandler()
if handler.is_enabled():
    print('Vibex is active')
else:
    print('Vibex is disabled (missing config or expired token)')

Verbose Mode

Enable verbose mode to see status messages when the handler initializes or encounters errors:

vibex_handler = VibexHandler(verbose=True)
logger.addHandler(vibex_handler)

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

vibex_sh-0.1.9.tar.gz (7.6 kB view details)

Uploaded Source

Built Distribution

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

vibex_sh-0.1.9-py3-none-any.whl (7.1 kB view details)

Uploaded Python 3

File details

Details for the file vibex_sh-0.1.9.tar.gz.

File metadata

  • Download URL: vibex_sh-0.1.9.tar.gz
  • Upload date:
  • Size: 7.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.8

File hashes

Hashes for vibex_sh-0.1.9.tar.gz
Algorithm Hash digest
SHA256 6f092dbb7c961d2a474c23cedf1ec3dcbf3419cf6578b04b974ef55b9bb6346a
MD5 6162938a7e585add9493f477ca340d4f
BLAKE2b-256 c533c08157abd780e22cb50aab4bb58aa27b71372edb596511849b173f544a9a

See more details on using hashes here.

File details

Details for the file vibex_sh-0.1.9-py3-none-any.whl.

File metadata

  • Download URL: vibex_sh-0.1.9-py3-none-any.whl
  • Upload date:
  • Size: 7.1 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.8

File hashes

Hashes for vibex_sh-0.1.9-py3-none-any.whl
Algorithm Hash digest
SHA256 34932a69b671e02ad052ca77558e96972c339c2153770ecc93516672bbd66054
MD5 88daea789757b05018bc62a0bb01d4f5
BLAKE2b-256 16b0e675d8de62a2b098ade1cb9d11f4f746b7adada4c44c00e974c31ce79c4a

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