System metrics are no longer collected by default when the correct dependency is installed. Use logfire.instrument_system_metrics() to enable system metrics collection. If you are simply using the old 'Basic System Metrics' dashboard, then no further code changes are required, but that dashboard will no longer work properly and you should create a new dashboard from the template named 'Basic System Metrics (Logfire)'. If you were using other collected metrics, see the documentation for how to collect those. By @alexmojaki in pydantic/logfire#373
OTEL_EXPORTER_OTLP_ENDPOINT is no longer just an alternative to LOGFIRE_BASE_URL. Setting OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_TRACES_ENDPOINT, and/or OTEL_EXPORTER_OTLP_METRICS_ENDPOINT will set up appropriate exporters in addition to sending to Logfire, which must be turned off separately if desired. These are basic exporters relying on OTEL defaults. In particular they don't use our custom retrying logic.
LOGFIRE_BASE_URL / logfire.configure(base_url=...) is now only intended for actual alternative Logfire backends, which are currently only available to Logfire developers, and unlike OTEL_EXPORTER_OTLP_ENDPOINT requires authenticating with Logfire.
Pending spans are only sent to logfire-specific exporters.
System metrics are no longer collected by default when the correct dependency is installed. Use logfire.instrument_system_metrics() to enable system metrics collection. If you are simply using the old 'Basic System Metrics' dashboard, then no further code changes are required, but that dashboard will no longer work properly and you should create a new dashboard from the template named 'Basic System Metrics (Logfire)'. If you were using other collected metrics, see the documentation for how to collect those. By @alexmojaki in pydantic/logfire#373
OTEL_EXPORTER_OTLP_ENDPOINT is no longer just an alternative to LOGFIRE_BASE_URL. Setting OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_TRACES_ENDPOINT, and/or OTEL_EXPORTER_OTLP_METRICS_ENDPOINT will set up appropriate exporters in addition to sending to Logfire, which must be turned off separately if desired. These are basic exporters relying on OTEL defaults. In particular they don't use our custom retrying logic.
LOGFIRE_BASE_URL / logfire.configure(base_url=...) is now only intended for actual alternative Logfire backends, which are currently only available to Logfire developers, and unlike OTEL_EXPORTER_OTLP_ENDPOINT requires authenticating with Logfire.
Pending spans are only sent to logfire-specific exporters.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
1 week ago
Bumps logfire-api from 0.49.0 to 0.51.0.
Release notes
Sourced from logfire-api's releases.
Changelog
Sourced from logfire-api's changelog.
Commits
108ae4bRelease v0.51.0 (#396)ec5f440Registeratexitcallback once perconfigureto prevent slowdown with each...a5c5ad8CheckLambdaRuntimeClientbefore logging tracebacks in `_ensure_flush_after...b7afdd5Disable ASGI send/receive spans by default (#371)ffe0c25Addlogfire.instrument_system_metrics()(#373)5d9a16fdocs: update mirascope third party integration docs with new v1 release + cus...b6b6822Don't auto-trace generators (#386)f2e87f3Add py.typed file to logfire-api (#379)0a393f8Update generated stubs (#389)181640fStop collecting package versions (#387)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show