# Character limit in fields longer then 1024 (truncated with ellipsis)

**URL:** <https://discuss.elastic.co/t/character-limit-in-fields-longer-then-1024-truncated-with-ellipsis/280415>\
**Category:** APM\
**Tags:** dotnet\
**Created:** [August 4, 2021, 10:41am UTC](https://discuss.elastic.co/t/character-limit-in-fields-longer-then-1024-truncated-with-ellipsis/280415 "2021-08-04T10:41:41Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\
**Post date:** [August 11, 2021, 2:03am UTC](https://discuss.elastic.co/t/character-limit-in-fields-longer-then-1024-truncated-with-ellipsis/280415/5 "2021-08-11T02:03:33Z")

</div>

Hi @GiladanoN,

The APM agents send data to APM server in formats that conform to JSON schemata. For example, the schema for spans is

> <https://github.com/elastic/apm-server/blob/cfc9d4c8043d489269e8d6678b6a567505962b9f/docs/spec/v2/span.json>

The schema defines a max length of 1024 for many of the string fields, in order to keep APM index sizes from growing large.

The .NET agent (and I think other agents too) hard limit the size of properties on trace types like `Span` and `Transaction` in line with the schema, and add an ellipsis to indicate a value has been truncated. Generally, fields with a max length are not configurable.

Are there particular fields you're using where max length configuration would be useful?

---

_[View the full topic](https://discuss.elastic.co/t/character-limit-in-fields-longer-then-1024-truncated-with-ellipsis/280415)._