# Backend and Frontend fields cannot be used in visualizations **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [February 20, 2018, 9:47pm UTC](https://discuss.elastic.co/t/backend-and-frontend-fields-cannot-be-used-in-visualizations/120729 "2018-02-20T21:47:17Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![darkl0rd](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@darkl0rd](https://discuss.elastic.co/u/darkl0rd)\ **Post date:** [February 20, 2018, 9:47pm UTC](https://discuss.elastic.co/t/backend-and-frontend-fields-cannot-be-used-in-visualizations/120729/1 "2018-02-20T21:47:17Z")
Two important fields in Traefik are the "traefik.access.frontend\_name" and "traefik.access.backend\_name" fields. Based on these fields one can identify the service which is being hit, especially in a Docker world this is really useful to be able to visualize. Currently fields defines these two as just being 'text', meaning one can't use these fields in visualizations within Kibana. Could they please be changed to Keywords instead? ---
**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\ **Post date:** [February 22, 2018, 5:57pm UTC](https://discuss.elastic.co/t/backend-and-frontend-fields-cannot-be-used-in-visualizations/120729/2 "2018-02-22T17:57:04Z")
Yes, or we could make it a multikey field, to support both use cases. Can you open a ticket against the beats repository, please? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 22, 2018, 6:05pm UTC](https://discuss.elastic.co/t/backend-and-frontend-fields-cannot-be-used-in-visualizations/120729/3 "2018-03-22T18:05:36Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.