Skip to main content
JaegerVFS mounts an existing Jaeger query service as read-only JSON files: each service becomes a folder with its operations and one file per trace. Set up the connection as in Jaeger setup.

Install

Configure

host is the query service’s base URL; it needs no credentials. defaultTraceLimit, defaultFromTimestamp and defaultToTimestamp bound each trace listing. The class ships in @struktoai/mirage-node only. In a YAML config or buildVfs('jaeger', ...), the same fields are snake_case (default_trace_limit).

Fields

string
default:"'http://localhost:16686'"
Jaeger query service URL.
number
default:"100"
The most traces one service’s traces/ listing shows, newest first. An older trace is still readable by its id.
string
Lower bound of trace listings, an ISO 8601 timestamp. Unset searches from the beginning.
string
Upper bound of trace listings, an ISO 8601 timestamp. Unset means now.
number
default:"DEFAULT_TIMEOUT"
Seconds a request may wait to connect, or between two reads of its answer, before it fails; a download that keeps flowing is never cut off.

Layout

  • services/: one folder per service Jaeger reports, including Jaeger’s own jaeger service when it traces itself.
  • operations.json: the service’s operation records, as Jaeger returns them.
  • traces/<trace-id>.json: the trace document Jaeger returns, with traceID, spans, processes and warnings.

Behavior

  • Read only: the mount has no write operations.
  • Trace listing: traces/ shows the newest defaultTraceLimit traces (100) of the service between defaultFromTimestamp and defaultToTimestamp; unset bounds search from the beginning up to now. A trace older than the listing is still readable by its id, as long as one of its spans comes from that service.
  • Missing paths: a service Jaeger does not know, a trace id that is not 16 or 32 hex digits, and a trace without a span from the addressed service are reported as missing.
  • Sizes: every listed file has an exact size, so ls -l, du and stat work without reading the files.

VFS.md

The VFS.md an agent reads with Jaeger mounted at /<path>.
Virtual FilesystemVFS Layout/<path>
Supported Unix Commands for VFSUnix commands work on each path as on a local filesystem, as far as the path supports them:Limitations of Unix Commands for VFSWhere a path differs from a local filesystem:Run man <cmd> or <cmd> --help for one command’s usage.