# Custom logs not appearing in visualization

**URL:** <https://discuss.elastic.co/t/custom-logs-not-appearing-in-visualization/239118>\
**Category:** Beats\
**Created:** [June 29, 2020, 1:33pm UTC](https://discuss.elastic.co/t/custom-logs-not-appearing-in-visualization/239118 "2020-06-29T13:33:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheNmaptomyHeartBeat](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@TheNmaptomyHeartBeat](https://discuss.elastic.co/u/TheNmaptomyHeartBeat)\
**Post date:** [June 29, 2020, 1:33pm UTC](https://discuss.elastic.co/t/custom-logs-not-appearing-in-visualization/239118/1 "2020-06-29T13:33:23Z")

</div>

Hi all,

I created custom logs in NGINX to log for `http.response.time` and `http.response.upstream.time`.

I updated the grok filter on the NGINX module pipeline for Filebeat.

I am receiving the data on the Filebeat-\* index and everything seems to work fine.

But when I got to create a TSVB visualization I am not able to find the above fields. Even though I am using the right index and I can see the data in the Discovery tab the fields are not coming up int he field box.

Is there something I am missing that needs to be done for the visualizations to work? I would like to get a dashboard of the response times for each requests.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/a/3a4a4309bec371244e3dbd9dfcb889fecd64dad5.png)

---

<div class="post-metadata">

**Author:** ![TheNmaptomyHeartBeat](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@TheNmaptomyHeartBeat](https://discuss.elastic.co/u/TheNmaptomyHeartBeat)\
**Post date:** [June 29, 2020, 1:53pm UTC](https://discuss.elastic.co/t/custom-logs-not-appearing-in-visualization/239118/2 "2020-06-29T13:53:34Z")

</div>

UPDATE:

I looked in the index pattern and noticed that it's identiyfing the field as a string. Even though I have the following in my filter:  
`%{NUMBER:http.response.time} %{NUMBER:nginx.response.upstream.time:}"`

I add `:long` to the end of those because the other patterns had and it resulted in an error, so it is picking it up as a string for some strange reason.

---

<div class="post-metadata">

**Author:** ![TheNmaptomyHeartBeat](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@TheNmaptomyHeartBeat](https://discuss.elastic.co/u/TheNmaptomyHeartBeat)\
**Post date:** [June 30, 2020, 12:56pm UTC](https://discuss.elastic.co/t/custom-logs-not-appearing-in-visualization/239118/3 "2020-06-30T12:56:43Z")

</div>

I ended up solving this issue by adding:  
`%{NUMBER:http.response.time:float} %{NUMBER:nginx.response.upstream.time:float}`.

Do note that the reason it didn't work for me is because the fields I created were already strings. You can change number to strings but not the other way around. So I created a new field and added `:float`.

---

<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 28, 2020, 2:56pm UTC](https://discuss.elastic.co/t/custom-logs-not-appearing-in-visualization/239118/4 "2020-07-28T14:56:48Z")

</div>

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