# Is there an option to set a different name (alias) other than the one on service\_name

**URL:** <https://discuss.elastic.co/t/is-there-an-option-to-set-a-different-name-alias-other-than-the-one-on-service-name/359213>\
**Category:** APM\
**Tags:** java\
**Created:** [May 9, 2024, 6:29pm UTC](https://discuss.elastic.co/t/is-there-an-option-to-set-a-different-name-alias-other-than-the-one-on-service-name/359213 "2024-05-09T18:29:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![minilik](https://avatars.discourse-cdn.com/v4/letter/m/9fc29f/32.png) [@minilik](https://discuss.elastic.co/u/minilik)\
**Post date:** [May 9, 2024, 6:29pm UTC](https://discuss.elastic.co/t/is-there-an-option-to-set-a-different-name-alias-other-than-the-one-on-service-name/359213/1 "2024-05-09T18:29:13Z")

</div>

Greetings!  
I'm trying to create some APM services from my java based servlets but I don't want to show the actual names on Kibana portal. Is there a way to create an alias for the Kibana portal different form the name set on elastic.apm.service\_name?

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [May 10, 2024, 12:58pm UTC](https://discuss.elastic.co/t/is-there-an-option-to-set-a-different-name-alias-other-than-the-one-on-service-name/359213/2 "2024-05-10T12:58:05Z")

</div>

Hi,

No, there isn't such feature available, however you should be able to use [ingest pipelines](https://www.elastic.co/guide/en/observability/current/apm-ingest-pipelines.html) for that purpose.

With that, you should be able to:

- change the values for `service.name`
- optionally keep the values in a separate attribute, for example in the `labels`.

As an alternative, you could also do the following:

- set `service.name` with an explicit value you'd like to see in Kibana
- set a global label in the APM agents configuration to store the value currently stored in `service.name`

This would not work if you rely on the service auto-detection feature in the Java agent, which is often used when multiple webapps are deployed on the same application server.