PHBourquin 039615641e Checks to passing/critical only after reaching a consecutive success/failure threshold (#5739) ...

A check may be set to become passing/critical only if a specified number of successive
checks return passing/critical in a row. Status will stay identical as before until
the threshold is reached.
This feature is available for HTTP, TCP, gRPC, Docker & Monitor checks.

2019-10-14 21:49:49 +01:00

..

alias_test.go

Move internal/ to sdk/ (#5568)

2019-03-27 08:54:56 -04:00

alias.go

agent: fix several data races and bugs related to node-local alias checks (#5876)

2019-05-24 13:36:56 -05:00

check_test.go

Checks to passing/critical only after reaching a consecutive success/failure threshold (#5739)

2019-10-14 21:49:49 +01:00

check.go

Checks to passing/critical only after reaching a consecutive success/failure threshold (#5739)

2019-10-14 21:49:49 +01:00

docker_unix.go

Decouple the code that executes checks from the agent

2017-10-25 11:18:07 +02:00

docker_windows.go

Decouple the code that executes checks from the agent

2017-10-25 11:18:07 +02:00

docker.go

Sets tty in docker client back to true, as a potential fix for docker exec weirdness

2017-11-05 09:44:55 -06:00

grpc_test.go

Checks to passing/critical only after reaching a consecutive success/failure threshold (#5739)

2019-10-14 21:49:49 +01:00

grpc.go

Expose HTTP-based paths through Connect proxy (#6446)

2019-09-25 20:55:52 -06:00