Skip to content

Avoid duplicate monitoring entries #129

@phirstgemini

Description

@phirstgemini

Currently we just add a new monitoring entry any time we capture_monitoring() in reducer. Would be better to avoid straight up duplicates.
We do record the header_id, so that helps, and maybe that's sufficient for now, but would be good to avoid out-and-out duplicates.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions