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.

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

Add MicroProfile Health guide #1483

Merged
merged 1 commit into from
Mar 15, 2019
Merged

Add MicroProfile Health guide #1483

merged 1 commit into from
Mar 15, 2019

Conversation

xstefank
Copy link
Member

@gsmet gsmet self-assigned this Mar 14, 2019
Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work. I added a bunch of suggestion inline, mostly about grammar and readability.

You can include them in a batch then commit them.

Happy to discuss them if you disagree on some!

include::./attributes.adoc[]
= {project-name} - MicroProfile Health

This guide demonstrates how can your {project-name} application utilize MicroProfile
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This guide demonstrates how can your {project-name} application utilize MicroProfile
This guide demonstrates how your {project-name} application can utilize the MicroProfile


== Architecture

In this guide, we build a simple REST application that exposes MP Health functionality at
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's use MicroProfile in full in the guide.

Suggested change
In this guide, we build a simple REST application that exposes MP Health functionality at
In this guide, we build a simple REST application that exposes MicroProfile Health functionalities at

== Architecture

In this guide, we build a simple REST application that exposes MP Health functionality at
`/health` endpoint according to the specification. It will also provide several other REST
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`/health` endpoint according to the specification. It will also provide several other REST
the `/health` endpoint according to the specification. It will also provide several other REST


== Running the health check

Importing `smallrye-health` extension directly exposes a single REST endpoint at
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Importing `smallrye-health` extension directly exposes a single REST endpoint at
Importing the `smallrye-health` extension directly exposes a single REST endpoint at

== Running the health check

Importing `smallrye-health` extension directly exposes a single REST endpoint at
`/health` of your application that can be used to run the health check procedures:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`/health` of your application that can be used to run the health check procedures:
`/health` that can be used to run the health check procedures:

== Negative health check procedure

In this section we create another health check procedure which simulates connection to
external service provider like database. For the simplicity reasons, we only determine
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
external service provider like database. For the simplicity reasons, we only determine
an external service provider such as a database. For simplicity reasons, we only determine

see in the `checks` array the newly added `Database connection health check` which is
down and the error message explaining why it failed.

As we shouldn't leave this application with health check in DOWN state and because we
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
As we shouldn't leave this application with health check in DOWN state and because we
As we shouldn't leave this application with a health check in DOWN state and because we


As we shouldn't leave this application with health check in DOWN state and because we
are running {project-name} dev mode you can add `database.up=true` in
`META-INF/microprofile-config.properties` and rerun the health check again --
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`META-INF/microprofile-config.properties` and rerun the health check again --
`src/main/resources/application.properties` and rerun the health check again --

This might need a change to the quickstart itself if you included the configuration file.


== Conclusion

MicroProfile Health provides a way how can your application distribute information
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
MicroProfile Health provides a way how can your application distribute information
MicroProfile Health provides a way for your application to distribute information

== Conclusion

MicroProfile Health provides a way how can your application distribute information
about its healthness state to typically state whether or not it is able to function properly.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove typically to simplify:

Suggested change
about its healthness state to typically state whether or not it is able to function properly.
about its healthness state to state whether or not it is able to function properly.

@gsmet gsmet merged commit 143007d into quarkusio:master Mar 15, 2019
@gsmet
Copy link
Member

gsmet commented Mar 15, 2019

Merged, thanks @xstefank!

@gsmet gsmet added this to the 0.12.0 milestone Mar 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants