Task's Micrometer tags are not injected into non-task metrics (E.g. System, CPU, Memory ...)

[tzolov]

The Task tags (task.name, task.exectuiont.id ...), inserted by the Task's MetricsAutoConfiguration implementation are not assigned to Task/Batch metrics.

JVM and System metrics such as process.cup., jvm.memory (and any non-task metrics) are missing the Task tags. This intern means that we can not compute the Memory, CPU and alike usage per Tasks.

[cppwfs]

I tried to build a sample on a 2.2.x of Boot and got a Caused by: java.lang.NoClassDefFoundError: reactor/util/retry/Retry We need either instructions on how to set this up properly and with which versions for the 2.2.x branch. Probably because of the prometheus rsocket.

[cppwfs]

@mminella Am I correct that Spring Cloud Task 2.2.x must support Spring Boot 2.2.x?

[mminella]

@cppwfs Yes since it's part of the previous Spring Cloud release train.

[cppwfs]

I merged this change . The change itself is ok. But scenario for a user to utilize metrics between 2.2.x and 2.3.x using prometheus is different. I think its just dependency management. So I will open a story for that in dataflow.spring.io.

Also I assume we need to forward port this to 2.3?