Janne Valkealahti

Cast from shell: ``` 09:42 $ export BUILD_ZOO_HANDLER_spring_cloud_dataflow_build_version=2.8.1 09:44 $ export BUILD_ZOO_HANDLER_spring_cloud_dataflow_build_buildname=spring-cloud-dataflow-build-main-release 09:44 $ export BUILD_ZOO_HANDLER_spring_cloud_dataflow_build_buildnumber=5 09:44 $ export BUILD_ZOO_HANDLER_spring_cloud_dataflow_common_version=2.8.1 09:44 $ export BUILD_ZOO_HANDLER_spring_cloud_dataflow_common_buildname=spring-cloud-dataflow-common-main-release 09:44 $ export BUILD_ZOO_HANDLER_spring_cloud_dataflow_common_buildnumber=5 09:44 $...

Might not be a bad idea at all. We should probably do a wider poc for generic observability/tracing features. I'd really appreciate to more easily to see and trace a...

We'd need to see logs from dataflow and skipper servers when you get this error. Also a stream definition would be helpful.

Thanks, this really looks interesting. What we've done with those tests which previously were automatically skipped by junit4 rules was just simply convert into `IT` tests and add junit5 tags....

It might be better to skip conversions for all classes which use `@ClassRule` as I realised there's no direct conversion to IT tests and we need to figure out actual...

We've been trying not to tweak setting too much as we don't know what user is running. On our normal apps we chose to re-enable those endpoints in apps itself....

Feels like this is related to #3978

So just to confirm, when you fail to get logs via scdf, you're able to see logs if you get those i.e. via `kubectl`?

@cppwfs As you've been handling these cases in a past would you know what happens here?

Have you tried latest dataflow release 2.8.1? We have moved ctr to get build with dataflow itself(to better align with api's) and we've fixed some issues around what you posted.