# User Agent Device Name

**URL:** <https://discuss.elastic.co/t/user-agent-device-name/180299>\
**Category:** APM\
**Tags:** rum\
**Created:** [May 9, 2019, 7:16am UTC](https://discuss.elastic.co/t/user-agent-device-name/180299 "2019-05-09T07:16:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![anushshukla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anushshukla/32/46173_2.png) [@anushshukla](https://discuss.elastic.co/u/anushshukla)\
**Post date:** [May 9, 2019, 7:16am UTC](https://discuss.elastic.co/t/user-agent-device-name/180299/1 "2019-05-09T07:16:14Z")

</div>

In the kibana logs of the RUM events (APM transaction events) at the Elastic Cloud APM servers, we have got the raw user agent string like

```
	Mozilla/5.0 (Linux; Android 7.1.1; SM-C900F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.90 Mobile Safari/537.36

```

whose corresponding device name comes as

> Generic Smartphone

On simply googling SM-C900F, we get which device it is, in this case, it is Samsung Galaxy C9 Pro SM-C900F.

If need be, I can post other such raw user agent string which are being tagged as Generic Smarthphone instead of their actual device name

---

<div class="post-metadata">

**Author:** ![Hamidreza](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hamidreza/32/21369_2.png) [@Hamidreza](https://discuss.elastic.co/u/Hamidreza)\
**Post date:** [May 9, 2019, 8:19am UTC](https://discuss.elastic.co/t/user-agent-device-name/180299/2 "2019-05-09T08:19:20Z")

</div>

Hi Anush,

This seems to be a limitation of our User Agent processor. I've created [this issue](https://github.com/elastic/elasticsearch/issues/41994) to request this improvement for the user agent processor.

Please feel free to comment on the issue or follow it for updates.

Cheers,  
Hamid

---

<div class="post-metadata">

**Author:** ![Siddharth\_Sharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/siddharth_sharma/32/45883_2.png) [@Siddharth\_Sharma](https://discuss.elastic.co/u/Siddharth_Sharma)\
**Post date:** [May 9, 2019, 9:46am UTC](https://discuss.elastic.co/t/user-agent-device-name/180299/3 "2019-05-09T09:46:46Z")

</div>

Hi @Hamidreza is there a way we can add our custom processing to the user agent before the document gets indexed?

---

<div class="post-metadata">

**Author:** ![Hamidreza](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hamidreza/32/21369_2.png) [@Hamidreza](https://discuss.elastic.co/u/Hamidreza)\
**Post date:** [May 9, 2019, 2:17pm UTC](https://discuss.elastic.co/t/user-agent-device-name/180299/4 "2019-05-09T14:17:52Z")

</div>

Hi Siddharth,

It is possible to define an ingest pipeline with multiple processors. In the [User Agent Processor documentation page](https://www.elastic.co/guide/en/elasticsearch/reference/master/user-agent-processor.html), for example, the pipeline is defined with only one processor, but you can add more to the `processors` field when you define the pipeline.

Please also make sure to [configure the APM server](https://www.elastic.co/guide/en/apm/server/7.0/configuring-ingest-node.html#apply-pipelines) to use the custom pipeline.

Cheers,  
Hamid

---

<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:** [May 30, 2019, 10:17am UTC](https://discuss.elastic.co/t/user-agent-device-name/180299/5 "2019-05-30T10:17:53Z")

</div>

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