Added functionality to allow for JSON file comparison output #584
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description
This PR extends the
compare.sh
script functionsrun_benchmark_comparison
andcompare
to allow for generation of JSON files - previously only CSVs were supportedRelated Tickets & Documents
Checklist before requesting a review
Testing
Tested locally using the OCP QE Elasticsearch instance and data generated with the Network Observability Prometheus and Elasticsearch (NOPE) tool
Set appropriate environmental variables and run:
$ source compare.sh $ run_benchmark_comparison
Test performed with the following env vars:
Console output (errors can be ignored, unrelated to this PR):
JSON file
node-density-heavy-da822ab1-3492-4dca-9f53-99f98018edc2.json
was generated successfully in the same directory as the script