Skip to content
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

Queued listener on secondary queue is also being displayed on the default queue graph under 'Queues' card #305

Closed
Winger15mk opened this issue Feb 1, 2024 · 4 comments · Fixed by #313
Assignees

Comments

@Winger15mk
Copy link

Pulse Version

1.0.0-beta11

Laravel Version

10.43.0

PHP Version

8.2

Livewire Version

3.2.0

Database Driver & Version

No response

Description

When a queued listener is triggered on a secondary queue, it is also showing within pulse as queued on default as well. The secondary queue jobs process perfectly and show as the purple processed line, however the line remains in the default queue. Horizon shows all outstanding jobs completed. Looking at the database pulse_aggregates table I see the duplicate records being created despite the technical processing working as expected.

Steps To Reproduce

  • Triggered a queued listener on a secondary queue to default using the ShouldQueue implementation. Define the queue within the listener itself (public $queue = 'secondary_queue';)
  • Pulse shows both the secondary queue and default queue graphs both with a spike displaying queued jobs, whereas should only show in the secondary.
@Winger15mk Winger15mk changed the title Queued listener on secondary queue is also being displayed on the default queue Queued listener on secondary queue is also being displayed on the default queue graph under 'Queues' card Feb 1, 2024
@Winger15mk
Copy link
Author

Screenshot 2024-02-06 at 20 54 00

Visual example of the issue

@timacdonald
Copy link
Member

@Winger15mk, we have seen this before and it has been a configuration issue.

Could you please provide your config/queue.php file for us to have a look at?

@Winger15mk
Copy link
Author

queue.txt

Note that I set queue connection to Redis in env

@timacdonald
Copy link
Member

Thanks. Looks like this is actually a Pulse issue, not a config issue as I first expected.

Should be fixed with #313

Will close this and we can follow along with the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants