Skip to content

Conversation

@filiphr
Copy link
Contributor

@filiphr filiphr commented Dec 2, 2018

  • When response status code is not 200 include the actual status code and the reason phrase
  • When response status code is 200 then include the entire response map as details for the health

* When response status code is not 200 include the actual status code and the reason phrase
* When response status code is 200 then include the entire response map as details for the health
@filiphr filiphr changed the base branch from master to 2.1.x December 2, 2018 15:33
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Dec 2, 2018
@bclozel bclozel self-assigned this Dec 3, 2018
@philwebb philwebb added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Dec 3, 2018
@philwebb philwebb added this to the 2.1.x milestone Dec 3, 2018
@bclozel bclozel changed the title Include health details in the ElasticsearchRestHealthIndicator Include health details in the Elasticsearch REST and Jest HealthIndicators Dec 11, 2018
bclozel pushed a commit that referenced this pull request Dec 11, 2018
This commit adds more information to the ElasticSearch REST
health indicator.

When the ES instance responds with an error HTTP status,
the health details now include the actual status code and reason phrase.
When the ES instance returns a HTTP 200 response, the entire response
map is used as health details.

See gh-15366
@bclozel bclozel modified the milestones: 2.1.x, 2.1.2 Dec 11, 2018
@bclozel bclozel closed this in 036aace Dec 11, 2018
@filiphr filiphr deleted the actuator-es-expose-details branch December 11, 2018 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: enhancement A general enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants