# Nginx module. upstream\_addr not available in nginx fields

**URL:** <https://discuss.elastic.co/t/nginx-module-upstream-addr-not-available-in-nginx-fields/183975>\
**Category:** Beats\
**Tags:** beats-module, filebeat\
**Created:** [June 3, 2019, 1:31pm UTC](https://discuss.elastic.co/t/nginx-module-upstream-addr-not-available-in-nginx-fields/183975 "2019-06-03T13:31:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ORich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/orich/32/21675_2.png) [@ORich](https://discuss.elastic.co/u/ORich)\
**Post date:** [June 3, 2019, 1:31pm UTC](https://discuss.elastic.co/t/nginx-module-upstream-addr-not-available-in-nginx-fields/183975/1 "2019-06-03T13:31:58Z")

</div>

Hi everyone,  
I cannot find any upstream\_addr related key in nginx fields [https://www.elastic.co/guide/en/beats/filebeat/7.1/exported-fields-nginx.html](https://www.elastic.co/guide/en/beats/filebeat/7.1/exported-fields-nginx.html)  
The upstream\_addr does contain the IP address and port, or the path to the UNIX-domain socket of the upstream server. This value is inserted in second position in my hereunder access.log file :

```auto
192.168.2.4 192.168.2.43:8000 - - [02/Jun/2019:04:05:31 +0200] "GET /_wss/.ws?v=5&ns=visioprod HTTP/1.1" 400 87 "-" - "0.004 msec"
192.168.2.4 192.168.2.45:8000 - - [02/Jun/2019:04:05:32 +0200] "GET /_wss/.ws?v=5&ns=visioprod HTTP/1.1" 101 92 "-" - "60.001 msec"
192.168.2.4 192.168.2.42:8000 - - [02/Jun/2019:04:05:46 +0200] "GET /_wss/.ws?v=5&ns=visioprod HTTP/1.1" 400 87 "-" - "0.003 msec"
192.168.2.4 192.168.2.47:8000 - - [02/Jun/2019:04:06:01 +0200] "GET /_wss/.ws?v=5&ns=visioprod HTTP/1.1" 400 87 "-" - "0.003 msec"
192.168.2.4 192.168.2.45:8000 - - [02/Jun/2019:04:06:33 +0200] "GET /_wss/.ws?v=5&ns=visioprod HTTP/1.1" 101 92 "-" - "60.003 msec"
192.168.2.4 192.168.2.43:8000 - - [02/Jun/2019:04:06:46 +0200] "GET /_wss/.ws?v=5&ns=visioprod HTTP/1.1" 400 87 "-" - "0.003 msec"
192.168.2.4 192.168.2.46:8000 - - [02/Jun/2019:04:07:01 +0200] "GET /_wss/.ws?v=5&ns=visioprod HTTP/1.1" 400 87 "-" - "0.002 msec"
192.168.2.4 192.168.2.45:8000 - - [02/Jun/2019:04:13:27 +0200] "GET /_wss/.ws?v=5&ns=visioprod HTTP/1.1" 101 92 "-" - "60.001 msec"
192.168.2.4 192.168.2.46:8000 - - [02/Jun/2019:04:42:50 +0200] "GET /_wss/.ws?v=5&ns=visioprod HTTP/1.1" 101 716 "-" - "2859.510 msec"
192.168.2.4 192.168.2.46:8000 - - [02/Jun/2019:04:44:46 +0200] "GET /_wss/.ws?v=5&ns=visioprod HTTP/1.1" 400 87 "-" - "0.003 msec"

```

---

<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 1, 2019, 1:31pm UTC](https://discuss.elastic.co/t/nginx-module-upstream-addr-not-available-in-nginx-fields/183975/2 "2019-07-01T13:31:59Z")

</div>

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