CheckcraftFind request logs by traceId in Kibana
The same endpoint may appear in thousands of log entries. Searching by a request identifier narrows the result to an operation, but only if the field, index and time range match your logging format.
You will know which value and field the search uses and can turn the selected log data into a repeatable check.
Use the actual field from your logs
Inspect a sample entry in _source. Your field might be traceId, trace.id or a custom path. Do not assume that a field shown in one service exists in another. Check the trace identifier returned by the request against the stored value.
Check time and event filters
A correct identifier can return no results if the index or time window is wrong. Start with the relevant period and verify the source connection. Add service, phase or message filters only after finding the operation. Several records for one trace can be normal.
Turn the result into a test
Select the event you want to validate, extract a JSON body if needed and add field rules. Keep a check that the required event exists. Otherwise a filter returning nothing can leave the intended business condition untested.
Repeat the check with ready-made files
Download the Checkcraft test case and two inputs. One input is valid, and the other contains a deliberate error. These synthetic examples are available without registration.
Run the example in Checkcraft
Create a collection, a check and a test case using the workspace tree context menu. Click Import in the test case editor and choose the downloaded test case. Open the added case, copy the valid JSON, click Paste data for analysis, then Run test case. Open Result to inspect the report.
Repeat with the broken JSON without changing the rules. The first run should pass and the second should fail. If you see a different outcome, check the selected data source, imported steps and report.
The example files were executed against the application source on 14 September 2026. Reference reports in English are available for the passing run and failing run. Sample names and literal data values do not change when you switch the interface language.
See the result on a small example first
Start with the sample, inspect the failure and then try a sanitized example from your own API. Free is available for Windows and Linux with no time limit.
Download FreeDownload and first runNo sign-up or email needed, the archive is ready in a couple of minutes. See the edition limits.