You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-apps/java-admin.md
+69-3Lines changed: 69 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -348,10 +348,76 @@ az group delete \
348
348
--resource-group $RESOURCE_GROUP
349
349
```
350
350
351
-
## Next steps
351
+
## Dependency
352
352
353
-
> [!div class="nextstepaction"]
354
-
> [Configure Admin for Spring settings](java-admin-for-spring-usage.md)
353
+
When you use the admin component in your own container app, you need to add the following dependency in your `pom.xml` file. Replace the version number with the latest version available on the [Maven Repository](https://search.maven.org/artifact/de.codecentric/spring-boot-admin-starter-client).
Starting with Spring Boot 2, endpoints other than health and info are not exposed by default. You can expose them by adding the following configuration in your `application.properties` file.
366
+
367
+
```properties
368
+
management.endpoints.web.exposure.include=*
369
+
management.endpoint.health.show-details=always
370
+
```
371
+
372
+
## Allowed configuration list for your Admin for Spring
373
+
374
+
The following list details the admin component properties you can configure foryour app. You can find more detailsin [Spring Boot Admin](https://docs.spring-boot-admin.com/current/server.html) docs.
375
+
376
+
| Property name | Description | Default value |
377
+
|--|--|--|
378
+
|`spring.boot.admin.server.enabled`| Enables the Spring Boot Admin Server. |`true`|
379
+
|`spring.boot.admin.context-path`| The path prefix where the Admin Server’s statics assets and API are served. Relative to the Dispatcher-Servlet. ||
380
+
|`spring.boot.admin.monitor.status-interval`| Time interval in milliseconds to check the status of instances. |`10,000ms`|
381
+
|`spring.boot.admin.monitor.status-lifetime`| Lifetime of status in milliseconds. The status isn't updated as long the last status isn’t expired. | 10,000 ms |
382
+
| `spring.boot.admin.monitor.info-interval` | Time interval in milliseconds to check the info of instances. | `1m` |
383
+
| `spring.boot.admin.monitor.info-lifetime` | Lifetime of info in minutes. The info isn't as long the last info isn’t expired. |`1m`|
384
+
|`spring.boot.admin.monitor.default-timeout`| Default timeout when making requests. Individual values for specific endpoints can be overridden using `spring.boot.admin.monitor.timeout.*`. |`10,000`|
385
+
|`spring.boot.admin.monitor.timeout.*`| Key-value pairs with the timeout per `endpointId`. | Defaults to `default-timeout` value. |
386
+
|`spring.boot.admin.monitor.default-retries`| Default number of retries for failed requests. Requests that modify data (`PUT`, `POST`, `PATCH`, `DELETE`) are never retried. Individual values for specific endpoints can be overridden using `spring.boot.admin.monitor.retries.*`. |`0`|
387
+
|`spring.boot.admin.monitor.retries.*`| Key-value pairs with the number of retries per `endpointId`. Requests that modify data (`PUT`, `POST`, `PATCH`, `DELETE`) are never retried. | Defaults to `default-retries` value. |
388
+
|`spring.boot.admin.metadata-keys-to-sanitize`| Metadata values forthe keys matching these regex patterns used to sanitizein all JSON output. Starting from Spring Boot 3, all actuator values are masked by default. For more information about how to configure the unsanitization process, see ([Sanitize Sensitive Values](https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#howto.actuator.sanitize-sensitive-values)). | `".**password$", ".\*secret$", ".\*key$", ".\*token$", ".\*credentials.**", ".*vcap_services$"` |
389
+
|`spring.boot.admin.probed-endpoints`| For Spring Boot 1.x client applications Spring Boot Admin probes for the specified endpoints using an `OPTIONS` request. If the path differs from the ID, you can specify this value as `id:path` (for example: `health:ping`) |`"health", "env", "metrics", "httptrace:trace", "threaddump:dump", "jolokia", "info", "logfile", "refresh", "flyway", "liquibase", "heapdump", "loggers", "auditevents"`|
390
+
|`spring.boot.admin.instance-proxy.ignored-headers`| Headers not to forwarded when making requests to clients. |`"Cookie", "Set-Cookie", "Authorization"`|
391
+
|`spring.boot.admin.ui.title`| The displayed page title. |`"Spring Boot Admin"`|
392
+
|`spring.boot.admin.ui.poll-timer.cache`| Polling duration in milliseconds to fetch new cache data. |`2500`|
393
+
|`spring.boot.admin.ui.poll-timer.datasource`| Polling duration in milliseconds to fetch new data source data. |`2500`|
394
+
|`spring.boot.admin.ui.poll-timer.gc`| Polling duration in milliseconds to fetch new gc data. |`2500`|
395
+
|`spring.boot.admin.ui.poll-timer.process`| Polling duration in milliseconds to fetch new process data. |`2500`|
396
+
|`spring.boot.admin.ui.poll-timer.memory`| Polling duration in milliseconds to fetch new memory data. |`2500`|
397
+
|`spring.boot.admin.ui.poll-timer.threads`| Polling duration in milliseconds to fetch new threads data. |`2500`|
398
+
|`spring.boot.admin.ui.poll-timer.logfile`| Polling duration in milliseconds to fetch new logfile data. |`1000`|
399
+
|`spring.boot.admin.ui.enable-toasts`| Enables or disables toast notifications. |`false`|
400
+
|`spring.boot.admin.ui.title`| Browser's window title value. | "" |
401
+
| `spring.boot.admin.ui.brand` | HTML code rendered in the navigation header and defaults to the Spring Boot Admin label. By default the Spring Boot Admin logo is followed by its name. | "" |
402
+
| `management.scheme` | Value that is substituted in the service URL used for accessing the actuator endpoints. | |
403
+
| `management.address` | Value that is substituted in the service URL used for accessing the actuator endpoints. | |
404
+
| `management.port` | Value that is substituted in the service URL used for accessing the actuator endpoints. | |
405
+
| `management.context-path` | Value that is appended to the service URL used for accessing the actuator endpoints. | `${spring.boot.admin.discovery.converter.management-context-path}` |
406
+
| `health.path` | Value that is appended to the service URL used for health checking. Ignored by the `EurekaServiceInstanceConverter`. | `${spring.boot.admin.discovery.converter.health-endpoint}` |
407
+
| `spring.boot.admin.discovery.enabled` | Enables the `DiscoveryClient` support for the admin server. | `true` |
408
+
| `spring.boot.admin.discovery.converter.management-context-path` | Value that is appended to the `service-url` of the discovered service when the `management-url` value is converted by the `DefaultServiceInstanceConverter`. | `/actuator` |
409
+
| `spring.boot.admin.discovery.converter.health-endpoint-path` | Value that is appended to the `management-url` of the discovered service when the `health-url` value is converted by the `DefaultServiceInstanceConverter`. | `"health"` |
410
+
| `spring.boot.admin.discovery.ignored-services` | Services that are ignored when using discovery and not registered as application. Supports simple patterns such as `"foo*"`, `"*bar"`, `"foo*bar*"`. | |
411
+
| `spring.boot.admin.discovery.services` | Services included when using discovery and registered as application. Supports simple patterns such as `"foo*"`, `"*bar"`, `"foo*bar*"`. | `"*"` |
412
+
| `spring.boot.admin.discovery.ignored-instances-metadata` | Services ignored if they contain at least one metadata item that matches patterns in this list. Supports patterns such as `"discoverable=false"`. | |
413
+
| `spring.boot.admin.discovery.instances-metadata` | Services included if they contain at least one metadata item that matches patterns in list. Supports patterns such as `"discoverable=true"`. | |
- Any other configurations under `logging.*` namespace should be forbidden. For example, writing log files by using `logging.file` should be forbidden.
0 commit comments