This test verifies that the subject correctly responds to the SIGHUP
signal, gracefully
reloading configuration changes.
- 2 TCP consumers are set up, each on separate hosts.
- Each subject is initially configured to send data to the first TCP consumer.
- A test line is sent to the subject.
- The subject's configuration file is updated to send data to the second TCP consumer.
- The
SIGHUP
signal is sent to the subject's project. - A second test line is sent to the subject.
- Assert that the first TCP server received the first line and the second TCP server received the second line.
Subject | Result |
---|---|
Filebeat | ❌ |
FluentBit | ❌ |
FluentD | ❌ |
Logstash | |
Splunk HF | ✅ |
Splunk UF | ✅ |
Vector | ✅ |
- Logstash failed the test because it does not gracefully reload change. Instead of performs a full restart, making Logstash unavaible for a period of time. Because of this it failed to receive the second line. In order for this test to pass we had to wait 30 seconds to send the second line.
You can run this test via:
test -t sighup_correctness