…kwinza)This PR was merged into the 5.4 branch.Discussion----------[Messenger] Add `WorkerMetadata` to `Worker` class.| Q             | A| ------------- | ---| Branch?       | 5.4| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Tickets       |Fixes#37736| License       | MIT| Doc PR        | -At the moment, there is no clean way to access the values of `transportNames` or recently introduced `queueNames` that the worker was configured with, although such data might be quite useful for logging/monitoring or other tasks.This PR attempts to fix that by adding a new and extensible way to provide additional information about a particular `Worker` object.So far, the following PRs could benefit from this change:-#43133-#42723**Use case example:**----- As I developer- When a message was consumed from transport with name `async`.- And the worker state is `idle`.- Then I want to reset services.**Before this PR**, the only solution not relying on using Reflection API would look like this:```php    private $servicesResetter;    private $receiversName;    private $actualReceiverName = null;    public function __construct(ServicesResetter $servicesResetter, array $receiversName)    {        $this->servicesResetter = $servicesResetter;        $this->receiversName = $receiversName;    }    public function saveReceiverName(AbstractWorkerMessageEvent $event): void    {        $this->actualReceiverName = $event->getReceiverName();    }    public function resetServices(WorkerRunningEvent $event): void    {        if (!$event->isWorkerIdle() && \in_array($this->actualReceiverName, $this->receiversName, true)) {            $this->servicesResetter->reset();        }        $this->actualReceiverName = null;    }    public static function getSubscribedEvents(): array    {        return [            WorkerMessageHandledEvent::class => ['saveReceiverName'],            WorkerMessageFailedEvent::class => ['saveReceiverName'],            WorkerRunningEvent::class => ['resetServices'],        ];    }```**With this PR**, one could simply use this to retrieve the transport name.```php$event->getWorker()->getWorkerMetadata()->getTransportName() === $this->transportName;```So the whole solution would look like this:```php    private $servicesResetter;    private $receiversName;    public function __construct(ServicesResetter $servicesResetter, array $receiversName)    {        $this->servicesResetter = $servicesResetter;        $this->receiversName = $receiversName;    }    public function resetServices(WorkerRunningEvent $event): void    {        $actualTransportName = $event->getWorker()->getWorkerMetadata()->getTransportName();        if (!$event->isWorkerIdle() || !in_array($actualTransportName, $this->receiversName, true)) {            return;        }        $this->servicesResetter->reset();    }    public static function getSubscribedEvents(): array    {        return [            WorkerRunningEvent::class => ['resetServices'],        ];    }```Commits-------583f85b [Messenger] Add WorkerMetadata to Worker class

…omie)This PR was merged into the 5.4 branch.Discussion----------[Messenger] Add worker metadata inside logs| Q             | A| ------------- | ---| Branch?       | 5.4| Bug fix?      | no| New feature?  | .| Deprecations? | no| Tickets       | Improve#42723| License       | MIT| Doc PR        | .Small PR related to one of my comment#42723 (comment) on the ticket PR: having this contextual info is valuable imhocc `@ruudk` `@okwinza` `@fabpot`Commits-------649cb10 [Messenger] Add worker metadata inside logs