# Why is the context for Span so limited compared to the context for Transaction?

**URL:** <https://discuss.elastic.co/t/why-is-the-context-for-span-so-limited-compared-to-the-context-for-transaction/274080>\
**Category:** APM\
**Tags:** ruby\
**Created:** [May 26, 2021, 2:58pm UTC](https://discuss.elastic.co/t/why-is-the-context-for-span-so-limited-compared-to-the-context-for-transaction/274080 "2021-05-26T14:58:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![m-s-santos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m-s-santos/32/88599_2.png) [@m-s-santos](https://discuss.elastic.co/u/m-s-santos)\
**Post date:** [May 26, 2021, 2:58pm UTC](https://discuss.elastic.co/t/why-is-the-context-for-span-so-limited-compared-to-the-context-for-transaction/274080/1 "2021-05-26T14:58:09Z")

</div>

Hello, I'm trying to add some custom information to a span's context; however, I can only change the context's labels. I'm wondering why there is this limitation. Also, the span's context can receive this `db` and `http` objects upon creation; why are those objects so limited as well? It has only a few fields of information. Is this an agent limitation or a limitation in APM in general?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 16, 2021, 10:58am UTC](https://discuss.elastic.co/t/why-is-the-context-for-span-so-limited-compared-to-the-context-for-transaction/274080/2 "2021-06-16T10:58:51Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.