Skip to content

Commit c3b268d

Browse files
author
Jay Bryant
committed
Made requested changes
Including removing the ==== fences around code blocks.
1 parent 5633ae5 commit c3b268d

File tree

8 files changed

+17
-208
lines changed

8 files changed

+17
-208
lines changed

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/cloud-foundry.adoc

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,12 @@ To use the endpoint, you must pass a valid UAA token with the request.
1515
=== Disabling Extended Cloud Foundry Actuator Support
1616
If you want to fully disable the `/cloudfoundryapplication` endpoints, you can add the following setting to your `application.properties` file:
1717

18-
====
1918
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
2019
----
2120
management:
2221
cloudfoundry:
2322
enabled: false
2423
----
25-
====
2624

2725

2826

@@ -31,14 +29,12 @@ If you want to fully disable the `/cloudfoundryapplication` endpoints, you can a
3129
By default, the security verification for `/cloudfoundryapplication` endpoints makes SSL calls to various Cloud Foundry services.
3230
If your Cloud Foundry UAA or Cloud Controller services use self-signed certificates, you need to set the following property:
3331

34-
====
3532
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
3633
----
3734
management:
3835
cloudfoundry:
3936
skip-ssl-validation: true
4037
----
41-
====
4238

4339

4440

@@ -51,9 +47,7 @@ If you expect the Cloud Foundry endpoints to always be available at `/cloudfound
5147
The configuration differs, depending on the web server in use.
5248
For Tomcat, you can add the following configuration:
5349

54-
====
5550
[source,java,indent=0,subs="verbatim"]
5651
----
5752
include::{docs-java}/actuator/cloudfoundry/customcontextpath/MyCloudFoundryConfiguration.java[]
5853
----
59-
====

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/enabling.adoc

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,6 @@ Actuators can generate a large amount of motion from a small change.
1111

1212
To add the actuator to a Maven-based project, add the following '`Starter`' dependency:
1313

14-
====
1514
[source,xml,indent=0,subs="verbatim"]
1615
----
1716
<dependencies>
@@ -21,15 +20,12 @@ To add the actuator to a Maven-based project, add the following '`Starter`' depe
2120
</dependency>
2221
</dependencies>
2322
----
24-
====
2523

2624
For Gradle, use the following declaration:
2725

28-
====
2926
[source,gradle,indent=0,subs="verbatim"]
3027
----
3128
dependencies {
3229
implementation 'org.springframework.boot:spring-boot-starter-actuator'
3330
}
3431
----
35-
====

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/endpoints.adoc

Lines changed: 6 additions & 60 deletions
Large diffs are not rendered by default.

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/jmx.adoc

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
[[actuator.jmx]]
22
== Monitoring and Management over JMX
33
Java Management Extensions (JMX) provide a standard mechanism to monitor and manage applications.
4-
By default, this feature is not enabled. You can turn it on by setting the configprop:spring.jmx.enabled[] configuration property to `true`.
4+
By default, this feature is not enabled.
5+
You can turn it on by setting the configprop:spring.jmx.enabled[] configuration property to `true`.
56
Spring Boot exposes the most suitable `MBeanServer` as a bean with an ID of `mbeanServer`.
67
Any of your beans that are annotated with Spring JMX annotations (`@ManagedResource`, `@ManagedAttribute`, or `@ManagedOperation`) are exposed to it.
78

@@ -26,7 +27,6 @@ To solve this problem, you can set the configprop:spring.jmx.unique-names[] prop
2627
You can also customize the JMX domain under which endpoints are exposed.
2728
The following settings show an example of doing so in `application.properties`:
2829

29-
====
3030
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
3131
----
3232
spring:
@@ -37,15 +37,13 @@ The following settings show an example of doing so in `application.properties`:
3737
jmx:
3838
domain: "com.example.myapp"
3939
----
40-
====
4140

4241

4342

4443
[[actuator.jmx.disable-jmx-endpoints]]
4544
=== Disabling JMX Endpoints
4645
If you do not want to expose endpoints over JMX, you can set the configprop:management.endpoints.jmx.exposure.exclude[] property to `*`, as the following example shows:
4746

48-
====
4947
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
5048
----
5149
management:
@@ -54,7 +52,6 @@ If you do not want to expose endpoints over JMX, you can set the configprop:mana
5452
exposure:
5553
exclude: "*"
5654
----
57-
====
5855

5956

6057

@@ -64,15 +61,13 @@ Jolokia is a JMX-HTTP bridge that provides an alternative method of accessing JM
6461
To use Jolokia, include a dependency to `org.jolokia:jolokia-core`.
6562
For example, with Maven, you would add the following dependency:
6663

67-
====
6864
[source,xml,indent=0,subs="verbatim"]
6965
----
7066
<dependency>
7167
<groupId>org.jolokia</groupId>
7268
<artifactId>jolokia-core</artifactId>
7369
</dependency>
7470
----
75-
====
7671

7772
You can then expose the Jolokia endpoint by adding `jolokia` or `*` to the configprop:management.endpoints.web.exposure.include[] property.
7873
You can then access it by using `/actuator/jolokia` on your management HTTP server.
@@ -89,7 +84,6 @@ Jolokia has a number of settings that you would traditionally configure by setti
8984
With Spring Boot, you can use your `application.properties` file.
9085
To do so, prefix the parameter with `management.endpoint.jolokia.config.`, as the following example shows:
9186

92-
====
9387
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
9488
----
9589
management:
@@ -98,20 +92,17 @@ To do so, prefix the parameter with `management.endpoint.jolokia.config.`, as th
9892
config:
9993
debug: true
10094
----
101-
====
10295

10396

10497

10598
[[actuator.jmx.jolokia.disabling]]
10699
==== Disabling Jolokia
107100
If you use Jolokia but do not want Spring Boot to configure it, set the configprop:management.endpoint.jolokia.enabled[] property to `false`, as follows:
108101

109-
====
110102
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
111103
----
112104
management:
113105
endpoint:
114106
jolokia:
115107
enabled: false
116108
----
117-
====

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/loggers.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,11 @@ These levels can be one of:
2121
=== Configure a Logger
2222
To configure a given logger, `POST` a partial entity to the resource's URI, as the following example shows:
2323

24-
====
2524
[source,json,indent=0,subs="verbatim"]
2625
----
2726
{
2827
"configuredLevel": "DEBUG"
2928
}
3029
----
31-
====
3230

3331
TIP: To "`reset`" the specific level of the logger (and use the default configuration instead), you can pass a value of `null` as the `configuredLevel`.

0 commit comments

Comments
 (0)