You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
abe43b2e83
This commit upgrades to the Couchbase SDK v3 which brings the following breaking changes: * Bootstrap hosts have been replaced by a connection string and the authentication is now mandatory. * A `Bucket` is no longer auto-configured. The `spring.couchbase.bucket.*` properties have been removed * `ClusterInfo` no longer exists and has been replaced by a dedicated API on `Cluster`. * `CouchbaseEnvironment` no longer exist in favour of `ClusterEnvironment`, the customizer has been renamed accordingly. * The bootstrap-related properties have been removed. Users requiring custom ports should supply the seed nodes and initialize a Cluster themselves. * The endpoints-related configuration has been consolidated in a single IO configuration. The Spring Data Couchbase provides an integration with the new SDK. This leads to the following changes: * A convenient `CouchbaseClientFactory` is auto-configured. * Repositories are configured against a bucket and a scope. Those can be set via configuration in `spring.data.couchbase.*`. * The default consistency property has been removed in favour of a more flexible annotation on the repository query methods instead. You can now specify different query consistency on a per method basis. * The `CacheManager` implementation is provided, as do other stores for consistency so a dependency on `couchbase-spring-cache` is no longer required. See gh-19893 Co-authored-by: Michael Nitschinger <michael@nitschinger.at> |
5 years ago | |
---|---|---|
.. | ||
src | 5 years ago | |
README.adoc | 5 years ago | |
build.gradle | 5 years ago |
README.adoc
= Spring Boot - Actuator Spring Boot Actuator includes a number of additional features to help you monitor and manage your application when it's pushed to production. You can choose to manage and monitor your application using HTTP or JMX endpoints. Auditing, health and metrics gathering can be automatically applied to your application. The https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#production-ready[user guide] covers the features in more detail. == Enabling the Actuator The simplest way to enable the features is to add a dependency to the `spring-boot-starter-actuator` '`Starter`'. To add the actuator to a Maven-based project, add the following '`Starter`' dependency: [source,xml,indent=0] ---- <dependencies> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-actuator</artifactId> </dependency> </dependencies> ---- For Gradle, use the following declaration: [indent=0] ---- dependencies { implementation 'org.springframework.boot:spring-boot-starter-actuator' } ---- == Features * **Endpoints** Actuator endpoints allow you to monitor and interact with your application. Spring Boot includes a number of built-in endpoints and you can also add your own. For example the `health` endpoint provides basic application health information. Run up a basic application and look at `/actuator/health`. * **Metrics** Spring Boot Actuator provides dimensional metrics by integrating with https://micrometer.io[Micrometer]. * **Audit** Spring Boot Actuator has a flexible audit framework that will publish events to an `AuditEventRepository`. Once Spring Security is in play it automatically publishes authentication events by default. This can be very useful for reporting, and also to implement a lock-out policy based on authentication failures.