-
Notifications
You must be signed in to change notification settings - Fork 117
Drop support for PHP 7.4 and 8.0, introduce support for PHP 8.4, fix semconv deprecations #315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
TraceAttributes::DB_OPERATION => $operationName, | ||
TraceAttributes::DB_NAMESPACE => $query->connection->getDatabaseName(), | ||
TraceAttributes::DB_OPERATION_NAME => $operationName, | ||
/** @phan-suppress-next-line PhanDeprecatedClassConstant */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea what to do if there is no replacement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess drop it is the best option
These changes look sensible, but I suspect that the semantic convention ones will run into the moratorium on changing produced telemetry. I don't fully understand the reasoning, but it's becoming a real pain for us: we created a bunch of packages (auto-instrumentation and such) at around semconv 1.24/1.25, and those packages are seemingly stuck on those versions until that moratorium is lifted. But in the meantime, new semconv versions have been released which deprecate some of those semconvs, and our static analysis tools complain. |
Are you happy with this now? I think I have also touched some of the same code in #327 (the build is quite green now), but let's merge this one first and I'll take care of any conflicts in my PR. |
6b997f2
to
66d1a18
Compare
@brettmc @ChrisLightfootWild I think PR is ready for your review. |
$record = (new LogRecord($log->message)) | ||
->setSeverityText($log->level) | ||
->setSeverityNumber(Psr3::severityNumber($log->level)) | ||
->setSeverityNumber(Severity::fromPsr3($log->level)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ChrisLightfootWild I think this requires API 1.1.0 and therefore dropping 8.0 support - how does that sound?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I've got the same dependency bumps in #269 so that's fine by me.
Would be good to maybe get this in first and then see if I can update my branch and move that forward a bit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, will merge!
No description provided.