seqcli trace command

[nblumhardt-ro]

Pretty-prints hierarchical traces:

A --json version, and MCP tool, serve automation use cases.

I like the --column mechanism, here. We can't do precisely the same thing for searches, since they can't currently include arbitrary expressions to attach to results server-side, but local expression evaluation would actually get us pretty far 🤔

seqcli trace [<args>]

Display a trace as a tree of spans

Example:
  seqcli trace -i 7d4dedcc73b18e449e0e4ea08cbe346d --column @SpanId --logs

Arguments:
  -i, --id=VALUE             The id of the trace to display
      --column=VALUE         A column to display preceding each event's
                               message; any Seq expression can be supplied,
                               for example `OrderId`, `@SpanKind`, or `@
                               Resource.service.name`; this argument can be
                               used multiple times, adding columns in order
      --logs                 Include log events in the trace, in addition to
                               spans
      --exceptions           Include exception details, where present
      --span-id=VALUE        The id of a span within the trace; when specified,
                                only the subtree rooted at this span is shown
      --json                 Print the trace as a single JSON document, with
                               spans and log events nested under their
                               parents (the default is plain text)
      --no-color             Don't colorize text output
      --force-color          Force redirected output to have ANSI color (
                               unless `--no-color` is also specified)
      --storage=VALUE        The folder where `SeqCli.json` and other data
                               will be stored; falls back to `SEQCLI_STORAGE_
                               PATH` from the environment, then the `seqcli
                               forwarder` service's configured storage path (
                               Windows only), then `/home/user01`
  -s, --server=VALUE         The URL of the Seq server; by default the `
                               connection.serverUrl` config value will be used
  -a, --apikey=VALUE         The API key to use when connecting to the server;
                               by default the `connection.apiKey` config
                               value will be used
      --profile=VALUE        A connection profile to use; by default the `
                               connection.serverUrl` and `connection.apiKey`
                               config values will be used
      --verbose              Print verbose output to `STDERR`

[nblumhardt-ro]

One TODO to go.

[nblumhardt-ro]

Might be better not to show the full CLI command, here; callers should typically provide --columns, so either we include examples or force seqcli trace --help usage.

[KodrAus]

Some of the test cases here look a bit dubious; they're likely to break in difficult to fix ways if we adjust the output format, but we can reconsider them if/when that actually happens.