i'm having an issue with certain logs fields being longer than 1024 chars.
When searching for the relevant log it comes up, but the relevant field is truncated, and the remainder of the text is replaced with an ellipsis character.
field/keyword: "loglog .. .. log…"
'…' char appears as the 1025 char in my log field).
We're using an APM Agent in our .Net application (classic / aspx),
and are querying the data using kibana's "discover" area.
Note- we're not getting errors when posting logs, but rather that they come up "partial" when we're querying them.
From reading up on this in various places:
- Increase setCustomContext context character limit
- Metadata | APM Server Reference [7.14] | Elastic
- 4096 characters input limitation! missing part of logs in message field
This would seem to be configurable somewhere somehow. Unfortunately i couldn't figure out where this change should be applied --- Tried looking at our .Net app's
web.config file, the
.cs file where we implement our
Application_Start() and the relevant
Agent APM instance....
Couldn't find a relevant configuration option in any of them, like a
truncateStringsAt or sanitization options, nor a
maxLength like property for the server's json config...
Where is this limitation coming from?
Is it a server-side config? (where the logs are sent to?)
Is there some other config on the App / Object's side that i'm missing or unfamiliar with?
Any help / pointers would be greatly appreciated !