Skip to content

ui: previous diagnostic bundle activations will prevent new triggers on statements list page #50824

@piyush-singh

Description

@piyush-singh

When a user activates a diagnostic bundle collection, they will see any fingerprints with collected bundles marked as "Ready":

image

This "Ready" indicator prevents users from triggering another bundle from the statements list page. Because bundles are never cleared today, this means that once a user has activated bundle collection once, they will never be able to trigger another activation from the statements list page again. Because bundles are persisted indefinitely, this state will persist even after the statement statistics are purged.

@Annebirzin - thoughts on a good way to resolve this? Perhaps we could both indicate that there are existing bundles separately from the ability to trigger a new one. I think that would result in only two states:

  • "Activate" the user has not told the cluster to collect a trace for this fingerprint - independent of if traces/bundles exist
  • "Waiting for Query" - we still need to let the user know if they have already triggered a bundle collection and prevent them from attempting to collect a new one.

The "Ready" status would be eliminated an instead replaced with a link to past bundles if we detect that any have been collected.

cc @florence-crl who mentioned this during our last Support sync.

Metadata

Metadata

Assignees

Labels

A-webui-queryperfC-cleanupTech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions