Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Unix & Linux ServerDistribution Release: Koozali SME Server 11.0(02.10.2026 um 13:29 Uhr)
•
Unix & Linux ServerSecurity: Zwei Probleme in OpenSSL (Ubuntu)(01.10.2026 um 23:37 Uhr)
•
Unix & Linux ServerSecurity: Ausführen beliebiger Kommandos in KCoreAddons (Ubuntu)(01.10.2026 um 23:37 Uhr)
•
Unix & Linux ServerSecurity: Denial of Service in rpcbind (SUSE)(01.10.2026 um 23:37 Uhr)
•
Unix & Linux ServerSecurity: Denial of Service in gnome-shell (SUSE)(01.10.2026 um 23:37 Uhr)
•
Unix & Linux ServerSecurity: Preisgabe von Informationen in libpcap (Red Hat)(01.10.2026 um 23:42 Uhr)
•
Unix & Linux ServerSecurity: Denial of Service in qt (Red Hat)(01.10.2026 um 23:42 Uhr)
•
Unix & Linux ServerSecurity: Zwei Probleme in dracut (Red Hat)(01.10.2026 um 23:42 Uhr)
•
Unix & Linux ServerSecurity: Mehrere Probleme in libX11 (SUSE)(02.10.2026 um 00:16 Uhr)
••
Unix & Linux ServerDistribution Release: Koozali SME Server 11.0(02.10.2026 um 13:29 Uhr)
•
Unix & Linux ServerSecurity: Zwei Probleme in OpenSSL (Ubuntu)(01.10.2026 um 23:37 Uhr)
•
Unix & Linux ServerSecurity: Ausführen beliebiger Kommandos in KCoreAddons (Ubuntu)(01.10.2026 um 23:37 Uhr)
•
Unix & Linux ServerSecurity: Denial of Service in rpcbind (SUSE)(01.10.2026 um 23:37 Uhr)
•
Unix & Linux ServerSecurity: Denial of Service in gnome-shell (SUSE)(01.10.2026 um 23:37 Uhr)
•
Unix & Linux ServerSecurity: Preisgabe von Informationen in libpcap (Red Hat)(01.10.2026 um 23:42 Uhr)
•
Unix & Linux ServerSecurity: Denial of Service in qt (Red Hat)(01.10.2026 um 23:42 Uhr)
•
Unix & Linux ServerSecurity: Zwei Probleme in dracut (Red Hat)(01.10.2026 um 23:42 Uhr)
•
Unix & Linux ServerSecurity: Mehrere Probleme in libX11 (SUSE)(02.10.2026 um 00:16 Uhr)
••
Intelligence View
⚡ tsecurity.de Intelligence

Different agent frameworks log 'input_tokens' differently. Here's the fix.

This is a submission for the Hermes Agent Challenge. I run agents on three different frameworks. Each one logs differently. One uses input_tokens. Another uses…

Beitrag
0
Seite
0
↗ Quelle (dev.to)
Social ReaktionenReagiere als Erste:r — dein Feedback zählt!

This is a submission for the Hermes Agent Challenge.



I run agents on three different frameworks. Each one logs differently. One uses input_tokens. Another uses prompt_tokens. A third uses tokens_prompt. My trace analysis code had to handle all three. Every new framework meant another alias to add everywhere.



That's trace-field-normalize.






One call per event






from trace_field_normalize import normalize_event

event = {"input_tokens": 42, "latency_ms": 350, "model_id": "claude-sonnet-4-5"}
result = normalize_event(event)
# {"tokens_in": 42, "duration_ms": 350, "model": "claude-sonnet-4-5"}






Unknown fields pass through unchanged. Nothing is dropped.






JSONL file in one call






from trace_field_normalize import normalize_file

events = normalize_file("raw_traces.jsonl", "normalized.jsonl")






Reads the source line by line, normalizes each event, writes to dest. Blank lines are skipped.






Default field map




















































Canonical Variants
tokens_in
input_tokens, prompt_tokens, tokens_prompt
tokens_out
output_tokens, completion_tokens, tokens_completion
cost_usd
cost, price_usd, usd, price
duration_ms
latency_ms, elapsed_ms, duration, latency
kind
event_type, type, event_kind
name
step, tool, tool_name, function_name
error
err, exception, error_message
model
model_id, model_name
lane
worker, agent_id, thread
timestamp
ts, time, created_at, event_time





Custom field maps






from trace_field_normalize import FieldMap, normalize_event

fm = FieldMap(
{"score": ["rating", "confidence"]},
include_defaults=True, # keep the built-in map too
)

event = {"rating": 0.95, "input_tokens": 100}
normalize_event(event, fm)
# {"score": 0.95, "tokens_in": 100}






include_defaults=False gives you a clean slate.






Canonical wins



If the event already has the canonical name, variants are left alone:




event = {"tokens_in": 99, "input_tokens": 42}
normalize_event(event)
# {"tokens_in": 99, "input_tokens": 42}









keep_original






normalize_event({"ts": 1700000000}, keep_original=True)
# {"timestamp": 1700000000, "ts": 1700000000}






Useful when downstream code still uses the old name.






Normalize a list






from trace_field_normalize import normalize_events

events = normalize_events(raw_event_list)






Returns a new list. Originals are not modified.






Zero dependencies



Standard library only: json, dataclasses, pathlib. Nothing else.




git clone https://github.com/MukundaKatta/trace-field-normalize
cd trace-field-normalize && pip install -e .






Repo: https://github.com/MukundaKatta/trace-field-normalize

Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Different agent frameworks log 'input_tokens' differently. Here's the fix.

Thematisch verwandte Begriffe: Different, agent, frameworks, inputtokens · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

💬 Kommentare werden geladen…
Zum Aktualisieren ziehen
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag