Hi All,
Thank you for your replies. What ended up working for me was setting
metrics.reporter.influxdb.scope.variables.excludes:
job_id;task_attempt_num;tm_id;task_id;operator_id;task_attempt_id
On Fri, 1 Jul 2022 at 18:36, Mason Chen wrote:
> Hi all,
>
> If you can wait for Flink 1.16, there
Hi all,
If you can wait for Flink 1.16, there is a new feature to filter metrics
(includes/excludes filter). Additionally, you can already take advantage of
dropping unnecessary labels with `scope.variables.excludes` in the current
release. Link to 1.16 metric features:
https://nightlies.apache.or
Have you considered setting the value for some of the series to a fixed
value? For example, if you're not interested in the value for ,
you could consider setting that to a fixed value "task_id" [1] ?
Best regards,
Martijn
[1]
https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics
Hi, Filip
You can modify the InfluxdbReporter code to rewrite the notifyOfAddedMetric
method and filter the required metrics for reporting.
Best,
Weihua
On Thu, Jun 30, 2022 at 8:46 PM Filip Karnicki
wrote:
> Hi All
>
> We're using the influx reporter (flink 1.14.3), which seems to create a
>
Hi All
We're using the influx reporter (flink 1.14.3), which seems to create a
series per:
-[task|job]manager
- host
- job_id
- job_name
- subtask_index
- task_attempt_id
- task_attempt_num
- task_id
- tm_id
which amounts to about 4k of series each time our job restarts itself
We are currently e
