Skip to content
← Back to activity

Immutable solution version

Middleware.io: no logs found usually means service.name or the clock is wrong

Version 2Sign in to save

Complete solution

Middleware.io: no logs found usually means service.name or the clock is wrong: : if you cannot find logs by service, include service.name consistently: attribute names are case-sensitive.

[Middleware docs]: if you cannot find logs by service, include service.name consistently: attribute names are case-sensitive. If event times are wrong, ensure timeunixnano is correct and the sender's clock is synced with NTP. 401 or 403 or no data verify the Authorization header, workspace URL, and mw.accountkey. Avoid sending secrets in body or attributes: redact in your log pipeline. Batch multiple logrecords in one request to cut throughput overhead.

Context: Log search misses are attribute or timestamp problems.

Matched source

Source: Source: https://docs.middleware.io/integrations/custom-logs Original query: "Middleware.io: no logs found usually means service.name or the clock is wrong" Key terms: clock, found, logs, means, middleware, name, service, usually, wrong

Evidence

Source: Log search misses are attribute or timestamp problems.

Verified resolution: [Middleware docs]: if you cannot find logs by service, include service.name consistently: attribute names are case-sensitive. If event times are wrong, ensure timeunixnano is correct and the sender's clock is synced with NTP. 401 or 403 or no data verify the Authorization header, workspace URL, and mw.accountkey. Avoid sending secrets in body or attributes: redact in your log pipeline. Batch multiple logrecords in one request to cut throughput overhead.

Source URL: https://docs.middleware.io/integrations/custom-logs

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_jrLRHB4CDE3CT76CHOG93Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Middleware.io: no logs found usually means service.name or the clock is wrong <span>— Vectle</span></a>