Similar to what was available in a previous version of WuppieFuzz, we would like to see a breakdown of the status codes per endpoint and method. An example of this can be seen below:
We would like to see a breakdown of the status codes per endpoint and method, whereby the adherence to the OpenAPI spec is shown. This means that (similar to the figure above) we can see for each status code in the spec if it has been detected during the fuzzing campaign, or if it was not reached. Additionally, we want to see status codes that were discovered which are not found in the spec.
This feature may require more than simply adding a visualization to Grafana. Namely, we need the information about hits and misses from the OpenAPI spec.
Similar to what was available in a previous version of WuppieFuzz, we would like to see a breakdown of the status codes per endpoint and method. An example of this can be seen below:
We would like to see a breakdown of the status codes per endpoint and method, whereby the adherence to the OpenAPI spec is shown. This means that (similar to the figure above) we can see for each status code in the spec if it has been detected during the fuzzing campaign, or if it was not reached. Additionally, we want to see status codes that were discovered which are not found in the spec.
This feature may require more than simply adding a visualization to Grafana. Namely, we need the information about hits and misses from the OpenAPI spec.