This is an automated email from the ASF dual-hosted git repository. ppalaga pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-quarkus-examples.git
commit 0b5aaede093c17995de15122a0189d22ae6ddf1c Author: James Netherton <[email protected]> AuthorDate: Mon Jun 14 09:31:14 2021 +0100 Adapt Observability docs page to Quarkus 2.0.0 --- health/README.adoc | 6 +++--- http-log/README.adoc | 4 ++-- observability/README.adoc | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/health/README.adoc b/health/README.adoc index 427eb6c..b3e1b3d 100644 --- a/health/README.adoc +++ b/health/README.adoc @@ -8,7 +8,7 @@ TIP: Check the https://camel.apache.org/camel-quarkus/latest/first-steps.html[Ca and other general information. The example has two routes. The timer route performs a given task at regular interval. For the sake of this example we'll say -that this task unexpectedly freezes the service from time to time. The details can be consulted at http://localhost:8080/health. +that this task unexpectedly freezes the service from time to time. The details can be consulted at http://localhost:8080/q/health. The custom health check is expected to report UNKNOWN on first consultation, then UP during 10 seconds, and finally DOWN so as to simulate that the service is frozen. @@ -16,7 +16,7 @@ The 2nd route is on purpose made to fail on startup by configuring netty to an u Camel supervising route controller will attempt to restart the route up till 10 times before exhausting. The routes health check will therefore report this route as DOWN until its exhausted where the states are changed to UNKNOWN. -The details can be seen at runtime via the following url from a web browser: http://localhost:8080/health. +The details can be seen at runtime via the following url from a web browser: http://localhost:8080/q/health. === Start in the Development mode @@ -31,7 +31,7 @@ workspace. Any modifications in your project will automatically take effect in t TIP: Please refer to the Development mode section of https://camel.apache.org/camel-quarkus/latest/first-steps.html#_development_mode[Camel Quarkus User guide] for more details. -You can check the health check status by calling the following url from a web browser: http://localhost:8080/health +You can check the health check status by calling the following url from a web browser: http://localhost:8080/q/health === Package and run the application diff --git a/http-log/README.adoc b/http-log/README.adoc index 68feaff..15c5ce0 100644 --- a/http-log/README.adoc +++ b/http-log/README.adoc @@ -39,8 +39,8 @@ From a web browser, you can call the two services via There is also health check and metrics available from the following urls: -- http://localhost:8080/health -- http://localhost:8080/metrics +- http://localhost:8080/q/health +- http://localhost:8080/q/metrics === Package and run the application diff --git a/observability/README.adoc b/observability/README.adoc index 4fc3f5b..55169fe 100644 --- a/observability/README.adoc +++ b/observability/README.adoc @@ -22,7 +22,7 @@ https://camel.apache.org/camel-quarkus/latest/first-steps.html#_development_mode === Metrics endpoint -Metrics are exposed on an HTTP endpoint at `/metrics`. You can also browse application specific metrics from the `/metrics/application` endpoint. +Metrics are exposed on an HTTP endpoint at `/q/metrics`. You can also browse application specific metrics from the `/q/metrics/application` endpoint. To view all Camel metrics do: @@ -41,7 +41,7 @@ $ curl -s -H"Accept: application/json" localhost:8080/q/metrics/application \ === Health endpoint -Camel provides some out of the box liveness and readiness checks. To see this working, interrogate the `/health/live` and `/health/ready` endpoints: +Camel provides some out of the box liveness and readiness checks. To see this working, interrogate the `/q/health/live` and `/q/health/ready` endpoints: [source,shell] ----
