elastic / elastic/support-diagnostics
import-monitoring.sh command is generated an error, exported monitoring data cannot be imported.
- Dominant language
- Java
- Stars
- 304
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
Hi team!
This is regarding [Importing Extracted Monitoring Data](https://github.com/elastic/support-diagnostics?tab=readme-ov-file#importing-extracted-monitoring-data).
I tested with 9.3.1 and 9.2.3 versions (export and import were performed in same version), both version showed below issue.
It seems `./export-monitoring.sh` command works, but `./import-monitoring.sh` generates below error so that the exported data cannot be imported.
```
12:12:08.224 [main] INFO co.elastic.support.BaseService - Diagnostic logger reconfigured for inclusion into archive
12:12:09.069 [main] ERROR co.elastic.support.util.ArchiveUtils - java.io.FileNotFoundException: ~/diagnostics-9.2.3/monitoring-export/extract/monitoring-export-20250923-055749/cluster_state.json (No such file or directory)
12:12:09.988 [main] INFO co.elastic.support.BaseService - Closing loggers.
```
Could you please take a look?
Thanks!
Contributor guide
Research direction
Start with the README section “Importing Extracted Monitoring Data” and reproduce the workflow with ./export-monitoring.sh followed by ./import-monitoring.sh on the 9.3.1 or 9.2.3 version. Trace the reported missing cluster_state.json under monitoring-export/extract and compare the generated archive paths. Done means exported monitoring data imports successfully without the FileNotFoundException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, shell
- Domain
- observability-sre, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100