v0.46.0

What's Changed

• Add logfire-api by @Kludex in #268
• Use exponential histogram buckets by @alexmojaki in #282
• Add attribute noting details of scrubbed values by @alexmojaki in #278
• Ensure force_flush at end of AWS Lambda invocation by @alexmojaki in #296

Full Changelog: v0.45.1...v0.46.0

v0.45.1

What's Changed

• Fix ignore no config warning message by @ba1mn in #292
• Ensure StaticFiles doesn't break instrument_fastapi by @alexmojaki in #294

New Contributors

• @ba1mn made their first contribution in #292

Full Changelog: v0.45.0...v0.45.1

v0.45.0

What's Changed

• Add scrubbing: ScrubbingOptions | False parameter to logfire.configure, replacing scrubbing_patterns and scrubbing_callback by @alexmojaki in #283
• Fix and test unmapped SQLModels by @alexmojaki in #286
• Optimize collect_package_info by @alexmojaki in #285

Full Changelog: v0.44.0...v0.45.0

v0.44.0

What's Changed

• Prevent 'dictionary changed size during iteration' error in install_auto_tracing by @alexmojaki in #277
• suppress_instrumentation when retrying exports by @alexmojaki in #279
• Log async stack in log_slow_async_callbacks by @alexmojaki in #280

Full Changelog: v0.43.0...v0.44.0

v0.43.0

What's Changed

• Breaking change: Remove default for modules parameter of install_auto_tracing by @alexmojaki in #261
• Breaking change: Check if logfire token is valid in separate thread, so logfire.configure won't block startup and will no longer raise an exception for an invalid token, by @alexmojaki in #274
• Remove logfire_api_session parameter from logfire.configure by @alexmojaki in #272
• Default the log level to error if the status code is error, and vice versa by @alexmojaki in #269
• Avoid importing gitpython by @alexmojaki in #260
• Only delete files on logfire clean by @Kludex in #267
• Bug fix: Logging arguments of a request to a FastAPI sub app by @sneakyPad in #259
• Fix query params not being in message by @alexmojaki in #271
• Replace 'Redacted' with 'Scrubbed' in 'Redacted due to...' by @alexmojaki in #273

New Contributors

• @sneakyPad made their first contribution in #259

Full Changelog: v0.42.0...v0.43.0

v0.42.0

What's Changed

• Improved handling of request errors when exporting by @alexmojaki in #252
• ignore_no_config setting added to pyproject.toml by @deepakdinesh1123 in #254
• Make logfire whoami respect the LOGFIRE_TOKEN env var by @alexmojaki in #256

New Contributors

• @sydney-runkle made their first contribution in #245

Full Changelog: v0.41.0...v0.42.0

v0.41.0

What's Changed

• Fix backfill command by @alexmojaki in #243
• Update Anthropic to use tools that are no longer in beta by @willbakst in #249
  • NOTE: Anthropic instrumentation now requires anthropic>=0.27.0

Full Changelog: v0.40.0...v0.41.0

v0.40.0

What's Changed

• BREAKING CHANGE: The processors parameter of logfire.configure() has been replaced by additional_span_processors. Passing processors will raise an error. Unlike processors, setting additional_span_processors to an empty sequence will not disable the default span processor which exports to Logfire. To do that, pass send_to_logfire=False. Similarly metric_readers has been replaced by additional_metric_reader. By @alexmojaki in #233
• Improve error raised when opentelemetry.instrumentation.django is not installed by @deepakdinesh1123 in #231
• Handle internal errors by @alexmojaki in #232

New Contributors

• @deepakdinesh1123 made their first contribution in #231

Full Changelog: v0.39.0...v0.40.0

v0.39.0

What's Changed

Add new methods for easier integration in #207:

• instrument_flask
• instrument_starlette
• instrument_aiohttp_client
• instrument_sqlalchemy
• instrument_pymongo
• instrument_redis

v0.38.0

What's Changed

BREAKING CHANGE: Calling logfire.info, logfire.error, logfire.span etc. will no longer automatically configure logfire if it hasn't been configured already. Instead it will emit a warning and not log anything.
Users must call logfire.configure() before they want logging to actually start, even if they don't pass any arguments to configure and all configuration is done by environment variables.
Using integrations like logfire.instrument_fastapi() before calling configure will also emit a warning but it will still set up the instrumentation, although it will not log anything until configure is called.

Full Changelog: v0.37.0...v0.38.0