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

TL;DR

If event times are wrong, ensure timeunixnano is correct and the sender's clock is synced with NTP. Avoid sending secrets in body or attributes: redact in your log pipeline. If you cannot find logs by service, include service.name consistently: attribute names are case-sensitive.

The error

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

Fix

1. If event times are wrong, ensure timeunixnano is correct and the sender's clock is synced with NTP. Expected: You get the expected result; the problem is gone.

2. Avoid sending secrets in body or attributes: redact in your log pipeline. Expected: You get the expected result; the problem is gone.

3. Re-run the original operation and confirm the error is gone. Expected: no error, normal output.

When to use

• You hit this exact error with Middleware.io.
• The symptom matches: no logs found usually means service.name or the clock is wrong.

When NOT to use

• A different error message from Middleware.io; the cause here is specific to this error.
• Unrelated Middleware.io issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Middleware.io. Source: https://docs.middleware.io/integrations/custom-logs.

Variant phrasings

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

Why it happens

Log search misses are attribute or timestamp problems.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

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