Skip to content
This repository has been archived by the owner on Sep 25, 2020. It is now read-only.

Healthcheck failures should have descriptive error messages #57

Open
rssathe opened this issue Sep 24, 2015 · 1 comment
Open

Healthcheck failures should have descriptive error messages #57

rssathe opened this issue Sep 24, 2015 · 1 comment

Comments

@rssathe
Copy link
Contributor

rssathe commented Sep 24, 2015

@kriskowal

tcurl --health -p 10.28.26.38:21305 chronotriggernotOk
rohan@hyperbahn04-sjc1:~$ tcurl -p 10.28.26.38:21305 chronotrigger foo
{ [TchannelNetworkError: tchannel socket error (ECONNREFUSED from connect): connect ECONNREFUSED]
  type: 'tchannel.network',
  message: 'tchannel socket error (ECONNREFUSED from connect): connect ECONNREFUSED',
  isErrorFrame: true,
  codeName: 'NetworkError',
  errorCode: 7,
  originalId: 2,
  name: 'TchannelNetworkError',
  fullType: 'tchannel.network' }
rohan@hyperbahn04-sjc1:~$ 

We should get something that notifies that hyperbahn can't connect to said service.

@Raynos
Copy link
Contributor

Raynos commented Sep 24, 2015

cc @malandrew @ShanniLi

We should fix the health check to tell us more then just the string "notOk"

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants