Offline event normalization, query and request correlation

tracelens

cli

moonbit

Download zip

Author

btlqql

Version

0.1.0

License

Apache-2.0

Repository

github.com/btlqql/moon-tracelens

Last updated

13 hours ago

Downloads

#Moon TraceLens

Offline log investigation, implemented in MoonBit with a JSON CLI and reusable library API.

Repository: https://github.com/btlqql/moon-tracelens
Package: btlqql/moon_tracelens@0.1.0
License: Apache-2.0
Release scope: 0.1.0 initial implementation. The broader competition proposal in docs/proposal.md is a reference design, not a claim that every planned capability is implemented.

#Implemented

JSONL and five-column pipe log ingestion; multiline stack continuations; epoch/RFC3339 timestamps; severity normalisation; source/line diagnostics; filters; request/service grouping; sorted timelines; error fractions and nearest-rank duration p95. scripts/files.mjs reads real selected log files.

#Build and run

Use MoonBit and Node.js 24. The core library supports JS, wasm, wasm-gc and native; the filesystem/HTTP/process CLI is JS only.

moon update
moon build --target js
moon run cmd/main --target js -- examples/scenario-1.json
node _build/js/debug/build/cmd/main/main.js examples/scenario-1.json

Pass - to read a UTF-8 JSON request from stdin. A single request must be at most 16 MiB. Successful requests print one JSON result; invalid requests exit nonzero. The host runner is a separate process and does not edit the input request file.

#Library use

moon add btlqql/moon_tracelens@0.1.0

In the consumer's moon.pkg:

import {
  "btlqql/moon_tracelens" @engine,
  "moonbitlang/core/json",
}

fn example(request : Json) -> Json raise {
  @engine.execute(request)
}

execute(Json) -> Json raise is the standard JSON boundary. from_json, Value::to_json, and run(Value) -> Value raise provide a typed semantic value interface. Object ordering is not significant; numeric values use finite Double. Public domain functions are listed in pkg.generated.mbti.

#Tests

moon test --target js
moon test --target wasm
moon test --target wasm-gc
moon test --target native  # requires a C compiler
moon build --target js
node scripts/check.mjs
python -B scripts/reference.py

There are 6 checked fixture cases in tests/cases.json, executed both in MoonBit white-box tests and through the actual Node CLI. Independent reference checks use Python's standard library or separately written algorithms. Fixtures are synthetic and are not presented as production adoption evidence. See input and output examples and current boundaries.

#Current boundaries

Offline batch analysis. Uppercase T/Z RFC3339, years 0001–9999, no leap seconds. Timestamps are seconds and duration_ms is milliseconds. Sources that fail event normalisation produce diagnostics; orphan pipe continuations are structural errors. No live tailing, rotation recovery or distributed tracing exporter.

See source and dependency attribution. This release does not establish competition eligibility or organizer acceptance.

InputError

source

pub(all) suberror InputError {
  InputError(String)
} derive(Eq, Show)

Value

source

pub(all) enum Value {
  Null
  Bool(Bool)
  Number(Double)
  String(String)
  Array(Array[Value])
  Object(Map[String, Value])
} derive(Eq, @moonbitlang/core/debug.Debug
Debug)

Value::stringify

source

fn Value::stringify(self : Value) -> String

Value::to_json

source

fn Value::to_json(self : Value) -> Json

execute

source

fn execute(request : Json) -> Json raise

from_json

source

fn from_json(value : Json) -> Value

run

source

fn run(request : Value) -> Value raise

timestamp

source

fn timestamp(value : Value) -> Double raise

Source Files

Site source Report issue Packages Build queue Skills Statistics

moon_tracelens

#Moon TraceLens

#Implemented

#Build and run

#Library use

#Tests

#Current boundaries

#InputError

#Value

#Value::stringify

#Value::to_json

#execute

#from_json

#run

#timestamp

Source Files

InputError

Value

Value::stringify

Value::to_json

execute

from_json

run

timestamp