5d6a821ae7
monitor: fix dropped error ( #7206 )
2020-02-11 10:57:50 +01:00
3dd0b59793
Allow users to configure either unstructured or JSON logging ( #7130 )
...
* hclog Allow users to choose between unstructured and JSON logging
2020-01-28 17:50:41 -06:00
8e673371df
test: ensure all TestAgent constructions use a constructor ( #6443 )
...
ensure all TestAgent constructions use a constructor to get start retries + test logs going to the right place
Fixes #6435
2019-09-05 10:24:36 -07:00
f8fa10fecb
refactor & add better retry logic to NewTestAgent ( #6363 )
...
Fixes #6361
2019-09-03 15:05:51 -07:00
a34f8c751e
Pass a testing.T into NewTestAgent and TestAgent.Start ( #5342 )
...
This way we can avoid unnecessary panics which cause other tests not to run.
This doesn't remove all the possibilities for panics causing other tests not to run, it just fixes the TestAgent
2019-02-14 10:59:14 -05:00
1dd8c378b9
Spelling ( #3958 )
...
* spelling: another
* spelling: autopilot
* spelling: beginning
* spelling: circonus
* spelling: default
* spelling: definition
* spelling: distance
* spelling: encountered
* spelling: enterprise
* spelling: expands
* spelling: exits
* spelling: formatting
* spelling: health
* spelling: hierarchy
* spelling: imposed
* spelling: independence
* spelling: inspect
* spelling: last
* spelling: latest
* spelling: client
* spelling: message
* spelling: minimum
* spelling: notify
* spelling: nonexistent
* spelling: operator
* spelling: payload
* spelling: preceded
* spelling: prepared
* spelling: programmatically
* spelling: required
* spelling: reconcile
* spelling: responses
* spelling: request
* spelling: response
* spelling: results
* spelling: retrieve
* spelling: service
* spelling: significantly
* spelling: specifies
* spelling: supported
* spelling: synchronization
* spelling: synchronous
* spelling: themselves
* spelling: unexpected
* spelling: validations
* spelling: value
2018-03-19 16:56:00 +00:00
69ebbf3e79
Fixes #3891 : agent monitor no longer unresponsive before logs stream.
...
The root cause is actually that the agent's streaming HTTP API didn't flush until the first log line was found which commonly was pretty soon since the default level is INFO. In cases where there were no logs immediately due to level for instance, the client gets stuck in the HTTP code waiting on a response packet from the server before we enter the loop that checks the shutdown channel from the signal handler.
This fix flushes the initial status immediately on the streaming endpoint which lets the client code get into it's expected state where it's listening for shutdown or log lines.
2018-02-19 21:53:10 +00:00
4f6abf1e72
commands: cleanup init
2017-10-18 02:39:10 +02:00
8f58a603ea
commands: get HTTP API flags for usage automatically
2017-10-18 00:08:45 +02:00
efab66e616
commands: cleanup help and synopsis.
...
* move Help and Synopsis to bottom
* make help and synopsis constants
* make sure help output is formatted
2017-10-18 00:08:45 +02:00
684362b1d0
Move monitor command to its own package
2017-10-18 00:08:45 +02:00
Lars Lehtonen