# Universal profiling APM integration - host.name not working

**URL:** <https://discuss.elastic.co/t/universal-profiling-apm-integration-host-name-not-working/356091>\
**Category:** Elastic Observability\
**Created:** [March 25, 2024, 10:55am UTC](https://discuss.elastic.co/t/universal-profiling-apm-integration-host-name-not-working/356091 "2024-03-25T10:55:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jakub\_Zilinek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jakub_zilinek/32/121850_2.png) [@Jakub\_Zilinek](https://discuss.elastic.co/u/Jakub_Zilinek)\
**Post date:** [March 25, 2024, 10:55am UTC](https://discuss.elastic.co/t/universal-profiling-apm-integration-host-name-not-working/356091/1 "2024-03-25T10:55:38Z")

</div>

Hello,  
We have currently set up this integration:

- PHP OTEL SDK -\> Otel collector -\> elastic APM.
- Universal Profiling set up in k8s

When looking at Transaction in APM we have this click through  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/4/d4ac3e4489ee62b5277dc1b6856fa0e3651dc15f.png)  
But after clicking at it it uses this query:  
`host.name: "aks-eocspot-38196108-vmss0000d1"`  
but the `host.name` has ALWAYS last 2 letters of the name capitalised, like this  
`host.name: "aks-eocspot-38196108-vmss0000D1"` so the query doesn't match anything.

Any idea where to look at ?

---

<div class="post-metadata">

**Author:** ![TimR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timr/32/126689_2.png) [@TimR](https://discuss.elastic.co/u/TimR)\
**Post date:** [April 10, 2024, 2:24pm UTC](https://discuss.elastic.co/t/universal-profiling-apm-integration-host-name-not-working/356091/2 "2024-04-10T14:24:18Z")

</div>

Hey Jakub

You are right, this is a known issue. Not lowercasing/normalizing `host.name ` would be correct.

There is an [ongoing discussion](https://github.com/elastic/beats/issues/38689) about this issue.

Additionally, to my knowledge there is currently no way to easily work around this. [KQL (the filter field) doesn't allow case-insensitive matching](https://github.com/elastic/kibana/issues/80591) for fields of type `keyword`, which is the field type of `host.name` in the profiling index.

Hopefully, the issue is solved soon.