What a running integration is doing

Camel 3 · 4:24

When a step of the hello integration starts failing, its logs, its failure counts and the trace of one message show what happened, in the terminal and in the admin UI.

Download the mp4Recorded on 2026.2

What it covers

A step that throws on every third message, published as 0.1.2
Checking that it runs, and its failed count, with weikio status
Following and filtering log lines with weikio logs by level and by query
Failed traces and the step that threw, with weikio traces
The Logs, Metrics and Traces sections of the integration in the admin UI
A failed trace, linked to its log lines and metrics

Commands in this video

Terminal

$ weikio run ./hello
$ weikio status sandbox/hello
$ weikio logs sandbox/hello --since 10m
$ weikio logs sandbox/hello -f
$ weikio logs sandbox/hello --level error
$ weikio logs sandbox/hello --query 'every third'
$ weikio traces sandbox/hello
$ weikio trace 56ec36911630f4d6da08910969d88f9f

Transcript

0:02This video shows how to see what a running integration is doing.
0:09On your machine, the sandbox/hello folder from the earlier videos.
0:14Your Weik.io installation holds the built versions, 0.1.1 latest and running.
0:22The deployment in devtest runs on agent dev.
0:25The agent starts one Java process per integration, so hello has this one.
0:31The deployment has run since the last video.
0:34Every three seconds the route writes a log line.
0:36The process keeps sending log lines, metrics, and traces to three stores.
0:44In the file: a timer tick, the message from a property, a log step.
0:50The edit makes every third message throw, on purpose.
0:54Because the step is groovy, the manifest names the dependency.
1:02weikio run uploads the folder, the installation builds a new version,
1:07and the command follows the log lines.
1:10The build ran on the installation, so 0.1.2 is now the latest.
1:18The deployment follows latest, so it takes the new version.
1:21The agent stops the old process and starts the new, which the followed lines show.
1:27From here, every third message fails, in the lines and in the drawing.
1:35weikio status sandbox/hello answers which version runs,
1:41on which agent, and since when.
1:44A line under the table counts messages, failures and memory for the last hour.
1:49That count already holds the failure the run introduced.
1:56Log lines stay in the installation, so weikio logs reads them from the log store.
2:02Asking for the last ten minutes prints the stored lines, oldest first.
2:06weikio logs with follow keeps printing lines as the route writes them.
2:12The failed message writes an error line into the tail, with a warning line under it.
2:19The level flag keeps the lines at that level and above, so the page holds errors.
2:25The query flag keeps only the lines holding the phrase you give it,
2:28here the failure's reason.
2:33Every message leaves a trace, and the listing prints them newest first.
2:38A trace is one message's path through the integration.
2:41The trace prints its start, its duration, its result, and its single step.
2:47The failed at line names the step and the reason.
2:51The trace ends by printing the logs command for this message.
2:59The Overview opens with the last hour weikio status counted,
3:03and the newest lines under it.
3:05The failed count stands right there, no command typed.
3:09The Logs page reads from the same store, with search,
3:12a level filter, and a histogram of the levels.
3:16Live tail turns the page into the following tail you saw in the terminal.
3:23Metrics opens on the figures every running copy is measured on,
3:27and the charts carry them over time.
3:30The Traces page lists the same traces as the command, one dot per message to pick.
3:36The trace page opens on the failure, step and reason,
3:40and reaches the message's log lines and metrics.
3:43A log line opens with its fields and a button for the trace of the message that wrote it.
3:52You edit the folder, then the installation builds a new version.
3:56The deployment follows latest, and the agent runs the version in a Java process.
4:01That process keeps sending log lines, metrics, and traces.
4:06The installation keeps the stores, and every command and page reads from them.
4:11Every tick of the timer answers what the integration is doing.

Next in this track

Camel 4 · 4:37 Where the values live