Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Sign in / Register
Toggle navigation
S
spring-boot
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
DEMO
spring-boot
Commits
2df4ead4
Commit
2df4ead4
authored
Jun 07, 2014
by
Phillip Webb
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Convert README.md -> README.adoc
parent
77d5453a
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
57 additions
and
7 deletions
+57
-7
README.adoc
spring-boot-actuator/README.adoc
+51
-0
README.adoc
...mples/spring-boot-sample-web-groovy-templates/README.adoc
+6
-0
README.md
...samples/spring-boot-sample-web-groovy-templates/README.md
+0
-7
No files found.
spring-boot-actuator/README.
md
→
spring-boot-actuator/README.
adoc
View file @
2df4ead4
# 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 endpoints, with JMX or even by remote shell (SSH or
Telnet). Auditing, health and metrics gathering can be automatically
applied to your application. The
[
user guide
](
http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#production-ready
)
= 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 endpoints, with JMX or even by remote shell (SSH or
Telnet). Auditing, health and metrics gathering can be automatically applied to your
application. The
http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#production-ready[user guide]
covers the features in more detail.
## Enabling the Actuator
== Enabling the Actuator
The simplest way to enable the features is to add a dependency to the
`spring-boot-starter-actuator`
"Starter POM". To add the actuator to a
Maven based
project, add the following "starter" dependency:
`spring-boot-starter-actuator`
``Starter POM''. To add the actuator to a Maven based
project, add the following "starter" dependency:
```
xml
[source,xml,indent=0]
----
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>
</dependencies>
```
----
For Gradle, use the declaration:
```
groovy
[indent=0]
----
dependencies {
compile("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
app and look at "/health" (and see "/mappings" for a list of other
HTTP endpoints).
*
**Metrics**
Spring Boot Actuator includes a metrics service with
"gauge" and "counter" support. A "gauge" records a single value; and
a "counter" records a delta (an increment or decrement). Metrics for
all HTTP requests are automatically recorded, so if you hit the
`metrics`
endpoint should should see a response similar to this:
*
**Audit**
Spring Boot Actuator has a flexible audit framework that
will publish events to an
`AuditService`
. 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.
*
**Process Monitoring**
In Spring Boot Actuator you can find
`ApplicationPidListener`
which creates file containing application PID
(by default in application directory and file name is
`application.pid`
).
----
== 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 `/health` (and see `/mappings` for
a list of other HTTP endpoints).
* **Metrics** Spring Boot Actuator includes a metrics service with ``gauge'' and
``counter'' support. A ``gauge'' records a single value; and a ``counter'' records a
delta (an increment or decrement). Metrics for all HTTP requests are automatically
recorded, so if you hit the `metrics` endpoint should should see a sensible response.
* **Audit** Spring Boot Actuator has a flexible audit framework that will publish events
to an `AuditService`. 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.
* **Process Monitoring** In Spring Boot Actuator you can find `ApplicationPidListener`
which creates file containing application PID (by default in application directory and
file name is `application.pid`).
spring-boot-samples/spring-boot-sample-web-groovy-templates/README.adoc
0 → 100644
View file @
2df4ead4
This sample application uses Spring Boot and
http://beta.groovy-lang.org/docs/groovy-2.3.1/html/documentation/markup-template-engine.html[Groovy templates]
in the View layer. The templates for this app live in `classpath:/templates/`, which is
the conventional location for Spring Boot. External configuration is available via
``spring.groovy.template.*''.
spring-boot-samples/spring-boot-sample-web-groovy-templates/README.md
deleted
100644 → 0
View file @
77d5453a
This sample application uses Spring Boot and
[
Groovy templates
](
http://beta.groovy-lang.org/docs/groovy-2.3.1/html/documentation/markup-template-engine.html
)
in the View layer. The templates for this app live in
`classpath:/templates/`
, which is the conventional location for Spring
Boot. External configuration is available via
"spring.groovy.template.
*
".
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment