-
Spike
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
NEW
-
NEW
-
-
Summary
Review the metrics generated by the collector and identify a strategy and changes
that can be removed to reduce the cardinality.
Acceptance Criteria
- Recommend if we should continue this as a feature or bug or reject the changes and why
- Gain consensus from the logging team of any plan or changes
- Document the plan or intended changes
- Create an epic and supporting JIRA tasks if appropriate
Questions
- Do we need to add API in order to preserve the current behavior as well as to allow 'reduced' behavior?
- Can we whitelist a set of metric to allow only those we understand and have determined to be useful
- Can we reduce labels to meet the objective
Notes
- One idea is that maybe we only really need sink/source metrics and some subset of transforms (i.e. discard count?)
- informs
-
OBSDA-1341 Reduce Vector cardinality
-
- New
-
- is duplicated by
-
LOG-8736 [spike] Investigate how to reduce the cardinality of metrics produced by the collector
-
- Closed
-