# How to upgrade apm-server processor to version 8.x

**URL:** <https://discuss.elastic.co/t/how-to-upgrade-apm-server-processor-to-version-8-x/371351>\
**Category:** APM\
**Tags:** server\
**Created:** [December 3, 2024, 2:28am UTC](https://discuss.elastic.co/t/how-to-upgrade-apm-server-processor-to-version-8-x/371351 "2024-12-03T02:28:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![leyao-daily](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leyao-daily/32/139644_2.png) [@leyao-daily](https://discuss.elastic.co/u/leyao-daily)\
**Post date:** [December 3, 2024, 2:28am UTC](https://discuss.elastic.co/t/how-to-upgrade-apm-server-processor-to-version-8-x/371351/1 "2024-12-03T02:28:49Z")

</div>

As the release node said in apm-server, the processor field will be removed in 8.x version. But our service is depended on the processor field, how can we upgrade to 8.x version, what is the new solution for this field.

---

<div class="post-metadata">

**Author:** ![Carson\_Ip](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carson_ip/32/115912_2.png) [@Carson\_Ip](https://discuss.elastic.co/u/Carson_Ip)\
**Post date:** [December 5, 2024, 5:28pm UTC](https://discuss.elastic.co/t/how-to-upgrade-apm-server-processor-to-version-8-x/371351/2 "2024-12-05T17:28:54Z")

</div>

Do you mind clarifying which processor field are you referring to? Is it the breaking change " Removed unsupported libbeat `processors` configuration [6474](https://github.com/elastic/apm-server/pull/6474)"?

---

<div class="post-metadata">

**Author:** ![leyao-daily](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leyao-daily/32/139644_2.png) [@leyao-daily](https://discuss.elastic.co/u/leyao-daily)\
**Post date:** [December 5, 2024, 5:47pm UTC](https://discuss.elastic.co/t/how-to-upgrade-apm-server-processor-to-version-8-x/371351/3 "2024-12-05T17:47:11Z")

</div>

Yes. I find it in the release note that apm-server will not support processors configuration in the future?

---

<div class="post-metadata">

**Author:** ![Carson\_Ip](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carson_ip/32/115912_2.png) [@Carson\_Ip](https://discuss.elastic.co/u/Carson_Ip)\
**Post date:** [December 5, 2024, 6:36pm UTC](https://discuss.elastic.co/t/how-to-upgrade-apm-server-processor-to-version-8-x/371351/4 "2024-12-05T18:36:17Z")

</div>

Correct. processors config is not supported in 8.x. What is your use case for it? In 8.x, you may use ES ingest pipelines to process data from apm-server.

---

<div class="post-metadata">

**Author:** ![leyao-daily](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leyao-daily/32/139644_2.png) [@leyao-daily](https://discuss.elastic.co/u/leyao-daily)\
**Post date:** [December 6, 2024, 2:57am UTC](https://discuss.elastic.co/t/how-to-upgrade-apm-server-processor-to-version-8-x/371351/5 "2024-12-06T02:57:45Z")

</div>

What confused me is that, in my understanding, filebeat/metricbeat and apm-server can be in similar field for different log collection. Why filebeat and metricbeat can still support the processor but apm-server can not.

We current use the following in apm configuration.

```auto
processors:

- add_host_metadata:
    netinfo.enabled: true

```

Do you have any advices for this?