It will not produce aggregates. But it may reduce the load a bit without
affecting correctness; some variables are not necessarily required for
preventing metrics from overriding each other; like the job/task name
(because the IDs are good enough).
On 12/10/2020 6:37 PM, Alexander Filipchik wr
Thank you for replying!
Will exclusion produce proper aggregates? If I drop subtask_index, will
resulting metric be a sum of all the subtasks, or it will be just data from
one that was reported the last?
Alex
On Thu, Dec 10, 2020 at 4:28 AM Chesnay Schepler wrote:
> There is no way to reduce t
There is no way to reduce the number of metrics.
The only thing you can do is exclude specific variables (e.g.,
task_name), like this:
metrics.reporter..scope.variables.exclude:task_name[;
On 12/9/2020 7:15 PM, Alexander Filipchik wrote:
Hi,
Is there a way to reduce cardinality (preaggregate
Hi,
Is there a way to reduce cardinality (preaggregate) metrics that are
emitted to Prom Push gateway?
Our metrics infra is struggling to digest per task stats. Any way we can
configure it to emit per stage aggregates?
Our current config:
metrics.scope.tm flink.taskmanager
metrics.scope.operator
