Insights Results Writer service should be able to consume and process these messages, because their format and content are correct.
These messages are stored in messages/normal subdirectory.
- 05_rules_hits.json report with exactly 5 rule hits for org_id=11789772
- 05_rules_hits_org_1.json report with exactly 5 rule hits for org_id=1
- 10_rules_hits.json report with exactly 10 rule hits for org_id=11789772
- 10_rules_hits_org_1.json report with exactly 10 rule hits for org_id=1
- 15_rules_hits.json report with exactly 15 rule hits for org_id=11789772
- 15_rules_hits_org_1.json report with exactly 15 rule hits for org_id=1
- big_results.json file with most reports created by joining several real data (no cluster is in the state when all rules fail)
- big_results_tutorial.json the same as report above, but with tutorial rule result
- big_results_no_skips.json the same as report above, but no skipped rules are stored
- big_results_no_skips_tutorial.json the same as report above, but with tutorial rule result
- big_results_org_1.json file with most reports, in this case for org_id=1
- no_hits.json data with no rule hits (ie. the cluster is healthy)
- no_hits_no_skips.json data with no rule hits and no skips (ie. there's no health check performed)
- result01.json artificially created report with specified number of rule hits
- result02.json artificially created report with specified number of rule hits
- result03.json artificially created report with specified number of rule hits
- result04.json artificially created report with specified number of rule hits
- result05.json artificially created report with specified number of rule hits
- tutorial_only.json report with only tutorial rule hit
Please note that all messages are stored in JSON format to be consumed by Insights Results Writer service. Additionally all messages are also stored in EDN format to be consumed by analysis tools.