Skip to main content

Squillify development is paused indefinitely. Read why, and discover what this experiment achieved. Read the story

MicroSkills Reference

Trace Identifier Normaliser

observability.normalize_trace_id

ProductionBounded custom (Class B)Deterministicstrictfastv1.0.0
No network

Overview

You send a log body and we return every trace id we recognise, each as lower-case 32-hex with the formats that matched it, where it first appears and how often. The formats are a closed list and there is no pattern field, because a caller-supplied expression over two megabytes is a denial of service with no safe version. The bare 32-hex and 16-hex formats are off unless you ask for them, since a bare hex run is equally likely to be a digest or a session token and returning tokens as trace ids is worse than returning nothing.

The same request carries a different-looking id in every hop: 32-hex in one service, 16-hex in the next, hyphenated in a third. Comparing them by eye is where correlation stops, and a hand-rolled pattern for the job is either wrong on the edges or a backtracking hazard on a large body.

Reliability

Fully deterministic: no clock, no network, no pattern compilation, and the scan is linear in the body for each enabled format. Ids are echoed and are not treated as secrets; malformed candidates report a position and a reason but never the offending text. Failures, none worth retrying unchanged: OBS_TRACE_TEXT_INVALID means text was empty. An absent or non-string text is a schema violation and is refused as an invalid request instead. OBS_TRACE_TEXT_TOO_LARGE means the body went past 2097152 bytes of UTF-8. OBS_TRACE_FORMAT_UNSUPPORTED means a name in formats is not one of the seven. OBS_TRACE_FORMATS_EMPTY means formats arrived as an empty array; omit it instead to get the default set. OBS_TRACE_ID_LIMIT_EXCEEDED means the body holds more than 10000 distinct ids, so split it. OBS_TRACE_OPTION_UNSUPPORTED means a property or a limit is not one we accept. OBS_TRACE_WORK_REFUSED means bytes times enabled formats went past 8388608, and the answer carries the projection, the budget and the byte ceiling for the formats you chose, so enabling fewer formats or sending less is a calculable fix. OBS_TRACE_OUTPUT_TOO_LARGE means the answer would not fit the inline response ceiling, so lower maxIds.

Context footprint

Echoes one row per distinct id plus one per malformed candidate; set includeInvalid false and lower maxIds for a compact answer. A successful call costs 2 execution credits.

When to use it

When you hold a log excerpt and want every trace id in it in one comparable form, with the positions to go back to.

When the identifier you want is not one of the seven formats, or when you need the trace itself rather than its id.

Scope

Note
Recognise trace ids in a log body under a closed set of propagation formats and return each one as lower-case 32-hex with its positions.

Non-goals

  • Does not accept a caller-supplied pattern, ever
  • Does not guess: bare hex runs are off unless you enable them
  • Does not fetch a trace, call a backend or read a clock
  • Does not redact the body or judge whether an id is sensitive
  • Does not correlate ids across two separate calls

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

parsing

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call2 credits

File handling

Accepts file_refProduces file_refMax input2 MB

How we handle your data

Sensitive output possible
What this means

This skill may receive sensitive content and may return submitted, transformed, extracted, or reformatted content.

Squillify guarantees
  • Runs inside Squillify
  • This skill runs inside Squillify.
  • Payloads are not sent to an external service by this skill.
  • Squillify does not permanently store submitted payloads.
  • Telemetry records metadata only, not submitted content.
  • Submitted payloads are not used for training.
  • Submitted payloads are not reviewed by humans.
  • This skill does not target sensitive data.
  • The response may contain submitted or transformed content.
Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

FieldTypeRequiredDescription
textstringYesRequired body of 1 to 2097152 UTF-8 bytes to search.
formatsarrayNoFrom 1 through 7 unique formats; omit it for the four labelled formats excluding bare hex.
limitsobjectNoClosed caps for distinct ids and malformed candidates; omit it for maxIds 10000 and maxInvalid 500.
includeInvalidbooleanNoWhether malformed candidates are listed; omit it for true.

Output schema

FieldTypeRequiredDescription
idsarrayYesOne closed id row per distinct canonical id, ordered by first position then id.
invalidarrayYesRecognised-but-rejected candidates, each a closed {reason, format, line, column, offset, length} object.
summaryobjectYesClosed scan summary with idCount, occurrenceCount, invalidCount, truncation flags, enabledFormats, scannedBytes and maxBytesForEnabledFormats.

API contract

POST /v1/execute
curl
curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"observability.normalize_trace_id","input":{"text":"traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01"}}'
Integrations
TypeScript SDK
import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("observability.normalize_trace_id", {"formats":["W3C_TRACEPARENT","HEX_32"],"text":"traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01\n"});

Errors

CodeHTTPRetryableDescription
VALIDATION_ERROR400NoThe request payload failed schema validation.
UNAUTHORIZED401NoMissing or invalid API key.
SKILL_NOT_ACCESSIBLE403NoThe API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN403NoThis skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE503YesPlan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND404NoThe requested skill or version does not exist.
TENANT_RATE_LIMITED429YesRequest rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED429YesPlan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT504YesExecution exceeded the allowed time budget.
OBS_TRACE_TEXT_INVALID400NoThe request payload failed this skill's input validation.
OBS_TRACE_TEXT_TOO_LARGE429NoA size, quota, rate, or time limit was exceeded.
OBS_TRACE_FORMAT_UNSUPPORTED400NoThe skill does not support the requested variant.
OBS_TRACE_FORMATS_EMPTY400NoThe request payload failed this skill's input validation.
OBS_TRACE_ID_LIMIT_EXCEEDED429NoA size, quota, rate, or time limit was exceeded.
OBS_TRACE_OPTION_UNSUPPORTED400NoThe skill does not support the requested variant.
OBS_TRACE_WORK_REFUSED429NoA size, quota, rate, or time limit was exceeded.
OBS_TRACE_OUTPUT_TOO_LARGE429NoA size, quota, rate, or time limit was exceeded.

Other limits

LimitValue
Recommended inline bytes32 KiB

Limitations

  • Does not accept a caller-supplied pattern, ever
  • Does not guess: bare hex runs are off unless you enable them
  • Does not fetch a trace, call a backend or read a clock
  • Does not redact the body or judge whether an id is sensitive
  • Does not correlate ids across two separate calls
  • Searching for an arbitrary identifier shape that is not one of the seven
  • Extracting structured fields from logs, which the parse skills answer

How to call

POST /v1/execute (requires authentication)

Request bodyjson
{
  "skillKey": "observability.normalize_trace_id",
  "input": {
    "formats": [
      "W3C_TRACEPARENT",
      "HEX_32"
    ],
    "text": "traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01\n"
  }
}

Examples

A traceparent recognised, counted once despite the bare form matching too

Inputjson
{
  "formats": [
    "W3C_TRACEPARENT",
    "HEX_32"
  ],
  "text": "traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01\n"
}
Expected outputjson
{
  "summary": {
    "idCount": 1,
    "occurrenceCount": 1,
    "invalidCount": 0,
    "truncated": false,
    "invalidTruncated": false,
    "enabledFormats": [
      "W3C_TRACEPARENT",
      "HEX_32"
    ],
    "scannedBytes": 69,
    "maxBytesForEnabledFormats": 4194304
  },
  "invalid": [],
  "ids": [
    {
      "traceId": "4bf92f3577b34da6a3ce929d0e0e4736",
      "formats": [
        "W3C_TRACEPARENT",
        "HEX_32"
      ],
      "padded": false,
      "occurrences": 1,
      "firstLine": 1,
      "firstColumn": 14,
      "firstOffset": 13,
      "length": 55,
      "spanId": null,
      "parentId": "00f067aa0ba902b7",
      "sampled": "01",
      "formatVersion": "00",
      "xrayEpochHex": null
    }
  ]
}
Tip
Both formats matched the same span, so the answer records both names against one occurrence rather than counting the id twice.

A 16-hex B3 id left-padded to the canonical width

Inputjson
{
  "formats": [
    "B3_SINGLE"
  ],
  "text": "b3=463ac35c9f6413ad-a2fb4a1d1a96d312-1\n"
}
Expected outputjson
{
  "summary": {
    "idCount": 1,
    "occurrenceCount": 1,
    "invalidCount": 0,
    "truncated": false,
    "invalidTruncated": false,
    "enabledFormats": [
      "B3_SINGLE"
    ],
    "scannedBytes": 39,
    "maxBytesForEnabledFormats": 8388608
  },
  "invalid": [],
  "ids": [
    {
      "traceId": "0000000000000000463ac35c9f6413ad",
      "formats": [
        "B3_SINGLE"
      ],
      "padded": true,
      "occurrences": 1,
      "firstLine": 1,
      "firstColumn": 4,
      "firstOffset": 3,
      "length": 35,
      "spanId": "a2fb4a1d1a96d312",
      "parentId": null,
      "sampled": "1",
      "formatVersion": null,
      "xrayEpochHex": null
    }
  ]
}
Tip
padded is true so you can tell a genuinely 32-hex id from a 16-hex one widened to match it.
  • Pull the trace ids out of a support-supplied log excerpt to look them up
  • Reconcile ids written by services using W3C, B3 and X-Ray propagation

Avoid for

  • Searching for an arbitrary identifier shape that is not one of the seven
  • Extracting structured fields from logs, which the parse skills answer

Composable with

Safety & privacy

  • Runs without calling any external service.
  • Your payloads are never stored permanently.
  • Telemetry captures metadata only — never your payload contents.
  • We never train models on your payloads.
  • No human reviews your payloads.

Tags

parsingobservabilitytracingcorrelation