SpringCloud | Microservice development | Microservice library

I'm trying to deploy a springcloud data flow stream like this:

REcently upgraded my springcloud data flow version and I cant configure the trigger sources.

2.1.0 version

I cant configure it now... any help please ?

Thanks!!

With the exciting releases of both SpringBoot 3.0.0-M1 and SpringCloud 2022.0.0-M1, I went ahead to bump the versions up.

https://spring.io/blog/2022/01/20/spring-boot-3-0-0-m1-is-now-available

https://spring.io/blog/2022/01/27/spring-cloud-2022-0-0-m1-codename-kilburn-has-been-released

While things worked perfectly fine on my SpringBoot 2.6.3 + Jubilee, the exact same code, with just the version change on the pom file to the new pair SpringBoot 3.0.0-M1 + SpringCloud 2022.0.0-M1, the following error is observed.

I am trying to find out if there exists a tool that can show realtime traffic flow for springboot + springcloud microservices for my architecture. While searching for such tool, I pondered upon Zipkin's dependency graph. Is it good enough? Or are there any better alternatives to show realtime flow of traffic?

Furthermore, I am seeking an opensource project more than a proprietary solution but I'd be open for either suggestions.

Our architecture is built upon springboot+springcloud hosted in AWS and OCI and using K8s as well.

Any advice/suggestion would be quite helpful.

Attached is zipkin's dependency which is somewhat similar to what I am trying to find out:

Looking forward to it. Kind regards.

I am using jhipster 7 with springboot 2.5.4 for microservice applications development (DEV env)

I have setup jhipster registry server running on my localhost port 8761 with docker's help.

I am trying to access jhipster central springcloud config on

http://localhost:8761/config/application/prod/main

from all my microservices and gateway.

However, I got the following 401 warning when starting any of my microservice and gateway:

Versions:

• SpringBoot: 2.3.12.RELEASE
• SpringCloud: Hoxton.SR12
• SpringCloud Starter Sleuth: 3.0.3
• Camel: 3.4.6

I want to add Sleuth to a pre-exisitng project that now makes use of ActiveMQ, previosuly it was jusing JMS. When I do, values from the ActiceMQ message get blocked/removed and (one being "filename" which is the key value for S2 requests). Other JMS values still seem to come through OK.

I need to understand why the non-JMS values are getting blocked/removed (I cannot find any information on what would be causing that to happen) to prevent the errors.

I know I can disbale Sleuth for JMS with spring.sleuth.messaging.jms.enabled=true but moving forwards I'd like to be able to trace the ActiveMQ/JMS code, so that workaround isn't particularly attractive.

As this is pre-exiting code, I'd also like to avoid having to re-write it if at all possible.

Has anyone gotten SPring Cloud Sleuth to work with ActiveMQ/JMS and can maybe point out where things are going wrong?

Edit:

Based on the initial response from Marcin, we found that the following version compile & execute, although significant problems do remain:

• SpringBoot: 2.4.8
• SpringCloud: 2020.0.3
• Camel: 3.7.5

Without Sleuth

ActiveMQ message details:

Log message ("filename", "CamelAwsS3Etag" etc present):

What is the format for passing in additional arguments or environment variables to the Data Flow Server in SCDF running on Kubernetes? When running locally in Docker Compose, I can do something like below, but not sure what the equivalent is when deploying to Kubernetes using the helm chart.

I'm trying to debug my application, but debugger not hitting this code block. Here is my custom gateway filter.

I'm trying to upgrade a project from SpringCloud BOM 2020.0.1 to 2020.0.2

When I change the BOM and re-build, I get an error in JUnit tests, saying that the new parameter spring.config.import is not set for configserver.

This project is not a ConfigServer, neither use ConfigServer (commented config client)

This is the reported error in tests contextLoads()