Skip to content
CheckcraftDownload
Practical workflow

Search logs by traceId online: find every line of a request and its errors

Checkcraft is a desktop app for checking APIs and logs without code, with a free edition. Download, no sign-up →

Paste a log fragment and the tool groups the lines by traceId, shows errors and warnings and tells you which request broke. It understands plain lines and JSON logs (level, message, trace.id fields), the traceparent format and traceId or X-Request-ID fields. The log never leaves your browser.

Checkcraft ·

Get help with your first test →

How to use it

Paste log lines into the field above. If you know the traceId, for example from the API response or a header, enter it and press Search: only the lines of that request remain, with errors marked. If you do not know it, leave the field empty: the tool finds every ID in the text and lists the requests with errors first. “Load an example” shows a typical case: the order is created with a 201, but the payment fails on the amount.

Which formats it reads

Text lines with ERROR, WARN, INFO and words like Exception or Traceback. JSON lines: the level comes from level, log.level or severity, the text from message or msg. IDs: the W3C traceparent header (a 32-hex-character trace-id), traceId, trace_id, the Elastic Common Schema trace.id field, X-Request-ID and correlationId. If your service uses another field name, just type the ID itself: the search matches any substring.

The same in a shell and in Kibana

On a server, grep and jq do the same. In Kibana Discover it is one KQL filter on the traceId field, optionally with the level.

# every line of one request across all files
grep -rh "4bf92f3577b34da6a3ce929d0e0e4736" /var/log/app/ | sort

# only the errors of this request
grep -rh "4bf92f3577b34da6a3ce929d0e0e4736" /var/log/app/ | grep -E "ERROR|Exception"

# JSON logs: jq on the trace.id field
jq -c 'select(.["trace.id"] == "4bf92f3577b34da6a3ce929d0e0e4736")' app.json.log

# Kibana Discover, KQL
trace.id : "4bf92f3577b34da6a3ce929d0e0e4736" and log.level : ("ERROR" or "WARN")

When the response is 200 but the log has an error

The trickiest case: the API answered 200 or 201, the test is green, and half a second later another service logged an ERROR: the payment failed, a message was not sent, the order is stuck in NEW. The response does not show it, so after important requests it is worth checking the logs by traceId. Done by hand after every run, this quickly becomes a chore people skip.

Check logs automatically

In Checkcraft the log is part of the check: the app takes the traceId from the response or a header, finds the records in Kibana or Elasticsearch and checks their fields the same way as the API response, for example that there is no ERROR and the amount matches. Linking responses to logs by traceId is unlimited in the free version; a source connects through Kibana Proxy or directly to Elasticsearch. No sign-up, Windows and Linux.

Next step

Repeat this on your own API

Checkcraft is a desktop app that saves API response checks without code and shows what did not match. Start with a sample, then use your own sanitized data. Free runs on Windows and Linux with no time limit.

Download FreeDownload and first run

No sign-up or email needed, the archive is ready in a couple of minutes. See the edition limits.

References

W3C Trace Context: the traceparent header · Elastic ECS: tracing fields · Elastic ECS: log fields

Start with the linked example and compare its result with your own test requirement.

Ask a person

Get help with your first test

Tell us what you want to test or where you got stuck. We can help you start Checkcraft, choose an example and understand your first run. You can ask before downloading.

The Telegram group is public: do not post passwords, tokens or confidential work data. A description of your task is enough to start.

You can also email us support@checkcraft.ru

No account required. We will reply by email. This is a support request, not a newsletter subscription.