Brett McBride

@agoallikmaa @cedricziel - all green again here. Today I have made the following changes which may be worth re-reviewing: 1. removed attributes (and added to the API, as discussed in...

This has come up as an issue at least once before: https://cloud-native.slack.com/archives/C01NFPCV44V/p1715862811690339 so I think this change is probably the right way to go. Our Laravel maintainer is on leave...

> Let me know if you'd rather me send a dedicated PR for the deprecation warnings, then I'll undo those changes. I fixed a bunch of those in the last...

released as v0.0.3

I think this is ready for review now, @open-telemetry/php-approvers There's an [OTEP](https://github.com/open-telemetry/oteps/pull/250) which looks like it will eventually specify a rules-based sampler, so to avoid a future config collision I've...

It's not a typo, but it could be a bug, depending on which Monolog [formatter](https://github.com/Seldaek/monolog/blob/main/doc/02-handlers-formatters-processors.md#formatters) you are using. A formatter must be used: https://github.com/Seldaek/monolog/blob/main/src/Monolog/Handler/FormattableHandlerTrait.php#L42 and we configure `NormalizerFormatter` as the...

@Spittal hi, sorry for the slow response. The build is failing on this PR, and it looks like the issue that Ago mentioned above

ping @Spittal

This is just what I need. Any progress on having this reviewed?

Hi @petrisorciprian-vitals yes, the [spec says](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/#general-sdk-configuration) it should work like that: > If “true”, **a no-op SDK implementation will be used** for all telemetry signals. Any other value or absence...