elastic / elastic/support-diagnostics
Logstash health_check API is always skipped regardless of mode
- Dominant language
- Java
- Stars
- 304
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
Diagnostics version: `9.3.1`
The logstash health report is always skipped, supposedly, due to its `mode` despite running in `full` mode. Subsequent APIs do get collected.
`WARN co.elastic.support.rest.RestEntryConfig - logstash_health_report was bypassed due to mode`
---
Based on the logic defined here, this should note get skipped with `full` mode
https://github.com/elastic/support-diagnostics/blob/085a381b814e2edb00dc8073a81a7bb4a35296b2/src/main/java/co/elastic/support/rest/RestEntryConfig.java#L57-L58
---
### **diag generated in interactive mode:**
`./diagnostics.sh `
**outcome:**
`cat logstash-local-diagnostics-20251217-212350/diagnostic_manifest.json`
```
{
"mode" : "full",
"product" : "logstash",
"flags" : "BaseInputs{outputDir='/Users/redacted/Downloads/diagnostics-9.3.1'},ElasticRestClientInputs: {host='localhost', port=9600, proxyHost='', proxyPort=8080, user='', isPassword=false, pkiKeystore='', isPkiPass=false, pkiKeystorePass='', proxyUser='', isProxyPass=false, isSsl=false, skipVerification=false, scheme='http'},DiagnosticInputs: {, diagType='logstash-local', mode='full', remoteUser='null', keyfile='', isKeyFilePass=false', trustRemote=false', knownHostsFile='', sudo=false', remotePort=22, runner='cli'}",
"diagnostic" : null,
"type" : "logstash_diagnostic",
"runner" : "cli",
"version" : "0.0.0",
"timestamp" : "2025-12-17T21:23:50.897Z"
}%
```
` head logstash-local-diagnostics-20251217-212350/diagnostics.log`
```diff
14:23:48.652 [main] INFO co.elastic.support.BaseService - Diagnostic logger reconfigured for inclusion into archive
-14:23:48.660 [main] WARN co.elastic.support.rest.RestEntryConfig - logstash_health_report was bypassed due to mode
```
### diag generated with explicit `full` mode
`./diagnostics.sh --mode full --host localhost --port 9600 --type logstash-local`
(also tested `logstash-api`)
**ouctome:**
`➜ cat logstash-local-diagnostics-20251217-213534/diagnostic_manifest.json`
```
{
"mode" : "full",
"product" : "logstash",
"flags" : "BaseInputs{outputDir='/Users/redacted/Downloads/diagnostics-9.3.1'},ElasticRestClientInputs: {host='localhost', port=9600, proxyHost='', proxyPort=8080, user='', isPassword=false, pkiKeystore='', isPkiPass=false, pkiKeystorePass='', proxyUser='', isProxyPass=false, isSsl=false, skipVerification=false, scheme='http'},DiagnosticInputs: {, diagType='logstash-local', mode='full', remoteUser='null', keyfile='', isKeyFilePass=false', trustRemote=false', knownHostsFile='', sudo=false', remotePort=22, runner='cli'}",
"diagnostic" : "9.3.1",
"type" : "logstash_diagnostic",
"runner" : "cli",
"version" : "0.0.0",
"timestamp" : "2025-12-17T21:35:34.928Z"
}%
```
`➜ head logstash-local-diagnostics-20251217-213534/diagnostics.log`
```diff
14:35:32.040 [main] INFO co.elastic.support.BaseService - Diagnostic logger reconfigured for inclusion into archive
14:35:32.041 [main] INFO co.elastic.support.diagnostics.commands.CheckDiagnosticVersion - Checking for diagnostic version updates.
-14:35:32.844 [main] WARN co.elastic.support.rest.RestEntryConfig - logstash_health_report was bypassed due to mode
```
Contributor guide
Assessment
This issue has not been assessed yet.