Skip to content

More queue health details from the CLI #146

@abrookins

Description

@abrookins

An Issue with a Curious Lack of Details

I know there's the docket snapshot command and there's also metrics collection, but I was trying to debug a runaway task earlier and was hoping for a way to see higher-level stats on tasks, like # of a specific task enqueued.

I first suspected I'd created a task that ended up reproducing itself, so I was trying to look around and guess that. But it was just a while loop that didn't break out correctly (wrong Redis key structure! 😂). Anyway, I was creating hundreds of tasks and some way to see a rollup on function would have been nice, so I could do a quick verify on whether that task was going crazy.

Curious what you folks think about that or if you'd rather avoid more work in the 'snapshot' area and push that to observation stacks, etc. Tracing might have helped, but I don't have my otel stack set up yet for these projects. 😅

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions