Scalingo/go-philae

Issues

• NSQProbe should use the same list of hosts as in go-utils/nsqlbproducer

  #14 opened 9 months ago by EtienneM
  1

• The etcd probe is not compatible with the new clientv3

  #6 opened 9 months ago by EtienneM
  3

• Upgrade dependency `gopkg.in/redis.v4` to `github.com/redis/go-redis/v9`

  #99 opened a year ago by EtienneM
  0

• Remove the dependency github.com/goware/httpmock

  #46 opened a year ago by EtienneM
  2

• [Elasticsearch] Cannot use the SystemPool

  #113 opened a year ago by johnsudaar
  0

• Migrate to swift/v2 client in swift-probe

  #87 opened 2 years ago by Soulou
  0

• Add a PostgreSQL probe

  #31 opened 5 years ago by EtienneM
  0

• Add GitLab probe

  #29 opened 5 years ago by brandon-welsch
  0

• [GitHub probe] Update url

  #28 opened 5 years ago by brandon-welsch
  1

• Prober is hiding the errors from the probes

  #24 opened 5 years ago by Soulou
  0

• TCP probe should have a better error management to know if DNS is failing or connection

  #22 opened 5 years ago by Soulou
  0

• [GitHub probe] status.github.com has been deprecated

  #19 opened 5 years ago by EtienneM
  0

• Add TCP Probe

  #15 opened 6 years ago by johnsudaar
  0

• The NSQ probe should accept a tls config to test https endpoint

  #12 opened 6 years ago by Soulou
  0

• The NSQ probe should take a NsqConfig as argument

  #11 opened 6 years ago by EtienneM
  0

• Philae handler logging should be configurable

  #9 opened 6 years ago by Soulou
  0

• The mongo probe is not compatible with ?ssl=true in the URL

  #7 opened 6 years ago by Soulou
  0

• [HTTP Probe] There should be a way to define an expected status code (ie. sometimes 404 is OK)

  #3 opened 7 years ago by Soulou
  1

• There should be short timeouts in checks, we don't want to wait an external service timing out

  #1 opened 7 years ago by Soulou
  1