After thread pools (17 Oct), this post covers structured logging: stable fields, required ids, cardinality, privacy, sampling, trace joins, format migration, retention and field-based alerts.

लघुटिप्पणीधर्मः: A Metrical Codification of Structured Logging (with English glosses)

What this post is about

Structured logging emits events as typed fields so they can be filtered aggregated and joined to traces.

Topics covered

1. Prose logs vs fields
2. Required envelope fields
3. Stable schema / cardinality
4. PII and secret redaction
5. Sampling strategy
6. Join to traces/metrics
7. Dual-write migrations
8. Retention vs metrics
9. Alerts on fields
10. Observability links

Sanskrit title

लघुटिप्पणीधर्मः = laghu-ṭippaṇī-dharmaḥ “dharma of light/structured notes”.

English

Minimizable; Sanskrit-first.

ग्राह्यम् / Keep

१. JSON/kv fields: not prose-only
२. trace_id required: on request paths
३. stable names: schema review
४. redact secrets: and minimize PII
५. sample successes: keep errors rich
६. retention policy: shorter for logs often
७. alert on fields: not brittle regex

त्याज्यम् / Avoid

• log full auth headers
• unique field name per user
• info log every packet at full QPS with no sample

पदच्छेदः
यदि लेखः केवलं गद्यं तदा यन्त्रं न पठति । लघुटिप्पणीधर्मस्तस्माद् क्षेत्रसत्यम् ॥१॥

Word-for-word

Gloss table

English sense
Structured logs use stable fields (JSON or key=value) so queries alerts and dashboards can filter without fragile regex on free text.

Context / topic
Topic: why structured logging. Distinct from privacy-log redaction treatise.

वृत्तमिति: ८-८-८-८।

पदच्छेदः
level timestamp service trace_id अनिवार्यम् । बिना तैः अन्वयः मृतः ॥२॥

Word-for-word

Gloss table

English sense
Every line should carry severity time service name and a correlation id that matches distributed context propagation.

Context / topic
Topic: required fields. Links to context propagation (29 Aug).

वृत्तमिति: ८-८-८-८।

पदच्छेदः
स्थिरक्षेत्रनामानि schemaवत् । चञ्चलkey cardinality दाहः ॥३॥

Word-for-word

Gloss table

English sense
Treat log field names as API. Do not put unbounded user ids into field names; put them in values with care.

Context / topic
Topic: schema and cardinality. Links to TSDB cardinality lesson.

वृत्तमिति: ८-८-८-८।

पदच्छेदः
गोप्यं मा स्फुटतु token password PII । गोपनीयतालेखो अत्रापि ॥४॥

Word-for-word

Gloss table

English sense
Structured does not mean dump everything. Redact secrets and minimize PII; sampling still applies.

Context / topic
Topic: privacy. Links to 11 Jul.

वृत्तमिति: ८-८-८-८।

पदच्छेदः
sample hot paths error paths पूर्णम् । अनन्तinfo भण्डारं दह्यते ॥५॥

Word-for-word

Gloss table

English sense
Sample successful high-QPS paths; keep errors and rare events at higher fidelity.

Context / topic
Topic: volume control.

वृत्तमिति: एकादशाक्षराः पादाः।

पदच्छेदः
trace span log exemplars मिलन्तु । त्रिपटलभेदः मा अन्धः ॥६॥

Word-for-word

Gloss table

English sense
Join logs to traces and metrics with shared ids. Observability without join keys is three silos.

Context / topic
Topic: correlation. Links to observability.

वृत्तमिति: ८-८-८-८।

पदच्छेदः
migration to structured dual-write काले । सहसान्त्ये दृश्यहानिः ॥७॥

Word-for-word

Gloss table

English sense
When migrating formats run dual parsers and keep old dashboards alive until cutover.

Context / topic
Topic: format migration.

वृत्तमिति: ८-८-८-८।

पदच्छेदः
PII retention logs भिद्यतां metrics । एक retention अन्धः ॥८॥

Word-for-word

Gloss table

English sense
Log retention is often shorter and more sensitive than metric retention. Align with data lifecycle dharma.

Context / topic
Topic: retention. Links to lifecycle (5 Sep).

वृत्तमिति: ८-८-८-८।

पदच्छेदः
alert from fields not regex poetry । भङ्गुरपद्यं रात्रौ हन्ति ॥९॥

Word-for-word

Gloss table

English sense
Page on structured predicates (status>=500). Regex on free text breaks when wording changes.

Context / topic
Topic: alerting on structure. Links to alerting.

वृत्तमिति: ८-८-८-८।

पदच्छेदः
अवलोकनशास्त्रं किं दृश्यम् लघुटिप्पणी कथं लेखः । सन्दर्भः कथं मिलति ॥१०॥

Word-for-word

Gloss table

English sense
Observability names the pillars; structured logging is how the log pillar stays queryable; context ids stitch pillars.

Context / topic
Topic: series links.

सन्धिः: अवलोकनं किम्; लेखः कथम्; सन्दर्भः मेलकः।

वृत्तमिति: एकादशाक्षराः पादाः।

पदच्छेदः
schema fields privacy sample join पञ्चकम् । एभिर्लघुटिप्पणी क्षेत्रसत्यसमन्विता ॥११॥

Word-for-word

Gloss table

English sense
Five limbs: field schema, required ids, privacy, volume sampling and cross-signal joins.

Context / topic
Topic: checklist.

वृत्तमिति: ८-८-८-८।

पदच्छेदः
इति लघुटिप्पणीधर्मसारः क्षेत्रसत्यसमन्वितः । मितं लेखं क्रियायोग्यं तन्त्रधर्मः स उच्यते ॥१२॥

Word-for-word

Gloss table

English sense
Closing: write logs machines can query and humans can trust without leaking the crown jewels.

Context / topic
Topic: close.

उपसंहारन्यायः: क्षेत्रैः लिख; गोप्यं मा; id देहि।

वृत्तमिति: ८-८-८-८।

१. Why structured
२. Envelope fields
३. Schema
४. Privacy
५. Sampling
६. Joins
७. Migration
८. Retention
९. Alerts
१०. Observability link
११. Five limbs
१२. Close

1. Prior: observability 2026-07-16; context 2026-08-29; privacy logs 2026-07-11; alerting 2026-07-17.
2. Domain: structured application logging.
3. English minimizable; Sanskrit-first.
4. Style: no em dash; no Oxford comma in English clauses.