Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add messaging health dependency to bom #2556

Merged
merged 2 commits into from
Nov 30, 2020
Merged

Add messaging health dependency to bom #2556

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ee6396b
Add messaging health dependency to bom
danielkec Nov 30, 2020
0c2c4cc
Typo fix
danielkec Nov 30, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions bom/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -675,6 +675,11 @@
<artifactId>helidon-microprofile-messaging</artifactId>
<version>${helidon.version}</version>
</dependency>
<dependency>
<groupId>io.helidon.microprofile.messaging</groupId>
<artifactId>helidon-microprofile-messaging-health</artifactId>
<version>${helidon.version}</version>
</dependency>

<!-- integrations -->
<dependency>
Expand Down
31 changes: 31 additions & 0 deletions docs/mp/reactivemessaging/01_introduction.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,3 +161,34 @@ Declare the following dependency in your project:
<artifactId>helidon-microprofile-messaging</artifactId>
</dependency>
----

=== Health check
Messaging in Helidon has built in health probes for liveness and readiness. To activate it
just add following dependency:
[source,xml]
----
<dependency>
<groupId>io.helidon.microprofile.messaging</groupId>
<artifactId>helidon-microprofile-messaging-health</artifactId>
</dependency>
----

* Liveness - channel is considered UP until `cancel` or `onError` signal is intercepted on it.
* Readiness - channel is considered DOWN until `onSubscribe` signal is intercepted on it.


If you check you health endpoints `/health/live` and `/health/ready` you will discover
danielkec marked this conversation as resolved.
Show resolved Hide resolved
Verdent marked this conversation as resolved.
Show resolved Hide resolved
every messaging channel to have its own probe.

[source,json]
----
{
"name": "messaging",
"state": "UP",
"status": "UP",
"data": {
"my-channel-1": "UP",
"my-channel-2": "UP"
}
}
----