# Hiding some span.subtype into Kibana's APM UI

**URL:** <https://discuss.elastic.co/t/hiding-some-span-subtype-into-kibanas-apm-ui/336580>\
**Category:** APM\
**Tags:** rum\
**Created:** [June 21, 2023, 12:49pm UTC](https://discuss.elastic.co/t/hiding-some-span-subtype-into-kibanas-apm-ui/336580 "2023-06-21T12:49:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Noxis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/noxis/32/70075_2.png) [@Noxis](https://discuss.elastic.co/u/Noxis)\
**Post date:** [June 21, 2023, 12:49pm UTC](https://discuss.elastic.co/t/hiding-some-span-subtype-into-kibanas-apm-ui/336580/1 "2023-06-21T12:49:55Z")

</div>

Hello,

We are currently using ECK to deploy our Elastic Stack in version 8.8.1 on GCP.  
I am actually configuring our applications to report to APM, we have multiple Vue and Quasar Frontends and some NestJS backends.

I was wondering if it's possible to disable in the APM interface of Kibana to disable some `span.subtype` ?

Because in the frontend to backend transactions, we are not really interested to see the script subtypes like in the following screenshot :

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/8/08d1d15b928b6b26ba99607763b315ce4562730b.png)

Seeing all the `script` subtypes 'pollute' our traces so I was wondering if it was possible to disable it in the charts.

Thanks a lot ! 🙂

---

<div class="post-metadata">

**Author:** ![Alberto\_Delgado](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alberto_delgado/32/98488_2.png) [@Alberto\_Delgado](https://discuss.elastic.co/u/Alberto_Delgado)\
**Post date:** [June 21, 2023, 2:35pm UTC](https://discuss.elastic.co/t/hiding-some-span-subtype-into-kibanas-apm-ui/336580/2 "2023-06-21T14:35:11Z")

</div>

Hi @Noxis,

Thanks for using Elastic APM!

There is no UI setting for hiding span.subtype in Kibana.

Let's explore possible alternatives:

At present, the RUM agent doesn't have any configuration that allows spans to be ignored. There is a [issue](https://github.com/elastic/apm-agent-rum-js/issues/1130) created but not yet prioritized.

Something that you could do is what a colleague suggested [here](https://github.com/elastic/apm-agent-rum-js/issues/1130#issuecomment-1328865624)

P.S. I'm assuming the waterfall of your screenshot belongs to a transaction created by [Javascript RUM agent](https://www.elastic.co/guide/en/apm/agent/rum-js/current/intro.html) and not to another APM agent, like the one from [Node.js](https://www.elastic.co/guide/en/apm/agent/nodejs/current/index.html)

Another feature that could help you to remove data you don't want is via [ingest pipelines](https://www.elastic.co/guide/en/apm/guide/current/ingest-pipelines.html)

Hope this helps you

Thanks,  
Alberto

---

<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:** [July 19, 2023, 2:35pm UTC](https://discuss.elastic.co/t/hiding-some-span-subtype-into-kibanas-apm-ui/336580/3 "2023-07-19T14:35:21Z")

</div>

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