Skip to content

o11y: protected timestamp record graph may be misleading #117989

Open
@ajstorm

Description

@ajstorm

As discovered through a DRT investigation, the Protected Timestamp Records graph in the DB Console may be misleading. We see this chart:

image

According to @stevendanna:

The graph records the number of "protected timestamp records" but it does it via the kv subscriber and the thing it seems to actually count is number of span configs that are covered by a protected timestamp.

So, in this case, I think it is going to end up report 3x the number of span configs we have

The last part is due to the fact that in the given case, we have 3 system-level protection policies.

More details can be found here.

Jira issue: CRDB-35446

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-cluster-observabilityRelated to cluster observabilityA-observability-infC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.O-testclusterIssues found or occurred on a test cluster, i.e. a long-running internal clusterP-2Issues/test failures with a fix SLA of 3 monthsT-observability

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions