I need your help about SpringBootAdmin server client settings

[Anvice]

version
Spring Boot 3.4.5 + Spring Boot Admin 3.4.5

hi guys，I encountered two problems，want help：

1、in 【Wallboard -> instance】，click instance, not entered instance, not displayed instance detail console view

Please note this：in instance view，url is 【http://localhost:8080/instances/[object%20Object]/details】，is the [object%20Object] in the URL because some client configuration has not been set properly?

2、in 【Applications】，click instance url, Jump to the client, 404

this's a 【application.ym】
application-server.yml.txt
application-client.yml.txt

[SteKoe]

Remove property-naming-strategy for Jackson and try again.

[Anvice]

Remove property-naming-strategy for Jackson and try again.

guys，I remove【spring.jackson.parser.property-naming-strategy】setting, however, the above issues have not been resolved.

I think These two issues are not related to jackson setting, because in 【jackson-databind-2.19.0】, 【spring.jackson.parser.property-naming-strategy】defaults to 【LOWER_CAMEL_CASE】.

[Anvice]

Remove property-naming-strategy for Jackson and try again.

guys，I remove【spring.jackson.parser.property-naming-strategy】setting, however, the above issues have not been resolved.

I think These two issues are not related to jackson setting, because in 【jackson-databind-2.19.0】, 【spring.jackson.parser.property-naming-strategy】defaults to 【LOWER_CAMEL_CASE】.

From the picture, it can be seen that the instance has been successfully registered, but it fails when 【entering the instance console】 and 【clicking on the instance details】. Therefore, I speculate that the problem may lie in the information pushed from the client to the server during registration, which appears to have caused the instance registration to be successful, but fails when 【entering the console】 and【 details through the instance】

[Anvice]

Remove property-naming-strategy for Jackson and try again.

guys，I remove【spring.jackson.parser.property-naming-strategy】setting, however, the above issues have not been resolved.
I think These two issues are not related to jackson setting, because in 【jackson-databind-2.19.0】, 【spring.jackson.parser.property-naming-strategy】defaults to 【LOWER_CAMEL_CASE】.

From the picture, it can be seen that the instance has been successfully registered, but it fails when 【entering the instance console】 and 【clicking on the instance details】. Therefore, I speculate that the problem may lie in the information pushed from the client to the server during registration, which appears to have caused the instance registration to be successful, but fails when 【entering the console】 and【 details through the instance】

This is the latest application.yml that I have adjusted

application-server.yml.txt

application-client.yml.txt

[Anvice]

version Spring Boot 3.4.5 + Spring Boot Admin 3.4.5

hi guys，I encountered two problems，want help：

1、in 【Wallboard -> instance】，click instance, not entered instance, not displayed instance detail console view

Please note this：in instance view，url is 【http://localhost:8080/instances/[object%20Object]/details】，is the [object%20Object] in the URL because some client configuration has not been set properly?

guys，the second issue has been resolved. Thoughts on the first question：

The path for obtaining client information on the server side. By default, the server obtains client information by accessing 【/instances】 requests. (The client registers with the server, and after successful registration, the server will create a unique value for the client called 【client ID】.). When the server needs to obtain client information, such as health information, it will request it【 http://localhost:8081/instances/clientID/actuator/health 】（Here, 【locahost:8081】 is the IP address of the server where the client is located.）

But now the server cannot retrieve the value of the client's 【contentID】

The problem is that it can be seen from the graph that 【client ID】 has actually been generated

[erikpetzold]

hi @Lucifer-Z

I think you are mixing things up here.

instance: your monitored application, running on port 8081
admin server: your Spring Boot Admin Server running on Port 8080

• it is correct that the server generates an id for each monitored instance (instanceId)
• "client" is an easy to confuse term here because there are many requests going in different directions
  • instance registers at admin server (using the SBA client module)
  • admin server calls actuator endpoint on instance (being the http client in this case)
  • frontend calls endpoints on admin server (being the http client in this case)
• the admin server will not request information from the instance with an id in the path - the instance does not offer these endpoints
  • instead, the frontend sends this request to the admin server, which will then forward it to the actuator endpoint of the matching instance
• so when you click in the url of your instance in the application list, it will just open that url and call your instance
  • if your instance does not handle GET requests to the root, then it displays an error message
  • the important thing to understand is, that you are navigating to the monitored instance when you click on the url
  • (if you click somewhere else in this line you open it in SBA UI)

[Anvice]

This problem is caused by multiple reasons, and currently one has been found: I used 【@EnableWebMvc】 in my custom class WebConfigurer(public class WebConfigurer implements WebMvcConfigurer {...})

In the old version（2.x.x）, if 【@EnableWebMvc】 is not added, an error will be reported: 【JSON parse error: Cannot deserialize value of type java.time.LocalDateTime from String "2020-06-04 15:07:54": Failed to deserialize java.time.LocalDateTime: (java.time.format.DateTimeParseException) Text '2020-06-04 15:07:54' could not be parsed at index 10; nested exception is com.fasterxml.jackson.databind.exc.InvalidFormatException: Cannot deserialize value of type java.time.LocalDateTime from String "2020-06-04 15:07:54": Failed to deserialize java.time.LocalDateTime: (java.time.format.DateTimeParseException) Text '2020-06-04 15:07:54' could not be parsed at index 10\n at [Source: (PushbackInputStream); line: 5, column: 17] (through reference chain: com.heartsuit.domain.Book["publishDate"]】

Therefore, when the project was upgraded from 2.X to 3.4.5, there was no to delete it, resulting in causing errors

but, Why does using 【@EnableWebMvc】 generate errors? I am currently unclear about the underlying logic

[Anvice]

Another reason is that I have set up my own 【MappingJackson2HttpMessageConverter】and【ObjectMapper】r to configure my global serialization return JSON processing.
At present, I have not detected any specific configuration issue, but it is indeed due to the settings of 【MappingJackson2HttpMessageConverter】and【ObjectMapper】 that caused the error

[Anvice]

Surprisingly, the customization of version 2.X on version 3.4.5 will encounter many unexpected issues. I need to focus on customizing settings

@erikpetzold guys，thanks for your help, which has given me a deeper understanding of SpringBootAdmin

[luguohaole]

package xxx;

import com.fasterxml.jackson.core.JsonGenerator;
import com.fasterxml.jackson.databind.JsonSerializer;
import com.fasterxml.jackson.databind.SerializerProvider;
import de.codecentric.boot.admin.server.domain.values.InstanceId;

import java.io.IOException;

/**

• InstanceIdSerializer

• @author ss
  */
  public class InstanceIdSerializer extends JsonSerializer {

  @OverRide
  public void serialize(InstanceId value, JsonGenerator gen, SerializerProvider serializers) throws IOException {
  if (value == null) {
  gen.writeNull();
  } else {
  // if InstanceId has getValue() return id
  gen.writeString(value.getValue());
  }
  }
  }

@bean
@ConditionalOnMissingBean
public Jackson2ObjectMapperBuilderCustomizer customizer() {
return builder -> {
builder.locale(Locale.CHINA);
builder.timeZone(TimeZone.getTimeZone(ASIA_SHANGHAI));
builder.simpleDateFormat(DatePattern.NORM_DATETIME_PATTERN);
builder.serializerByType(Long.class, ToStringSerializer.instance);
builder.modules(new CustomJavaTimeModule());
// add
builder.serializerByType(InstanceId.class, new InstanceIdSerializer());
};
}

this is ok .