[filebeat] broken dashboard in envoyproxy module

[faec]

• Version: 7.2.0
• Operating System: Linux
• Discuss Forum URL: https://discuss.elastic.co/t/filebeat-7-2-0-autodiscover-configuration-issues
• Steps to Reproduce: Enable the dashboards in the envoyproxy module

This came from the discuss post above. The screenshots show the envoyproxy dashboards failing on reference to several invalid fields. Checking the repo confirms those fields are incorrectly referenced by Filebeat-Envoyproxy-Overview.json. This looks like probably a simple fix, changing "url.domain.keyword" to "url.domain" and similarly for all the other ...keyword fields.

[dnmahendra]

I see this issue is marked as closed but I don't think it's working. The dashboard is still broken. And on top of that I am seeing these warnings constantly on the filebeat pods

elasticsearch/client.go:527	Cannot index event publisher.Event{Content:beat.Event{Timestamp:time.Time{wall:0xbd56d8a, ext:63702806784, loc:(*time.Location)(nil)}, Meta:common.MapStr{"pipeline":"filebeat-7.2.0-envoyproxy-log-pipeline-entry"}, Fields:common.MapStr{"agent":common.MapStr{"ephemeral_id":"66376294-adb1-4ec6-b76e-cdb8fb98d9d4", "hostname":"filebeat-2gknk", "id":"d9afe4cf-1b8e-4d61-87f2-4fdca4e1e92c", "type":"filebeat", "version":"7.2.0"}, "cloud":common.MapStr{"availability_zone":"ap-southeast-2a", "instance":common.MapStr{"id":"i-07f28a6d5afe3edb9"}, "machine":common.MapStr{"type":"m5.large"}, "provider":"aws", "region":"ap-southeast-2"}, "ecs":common.MapStr{"version":"1.0.0"}, "event":common.MapStr{"dataset":"envoyproxy.log", "module":"envoyproxy"}, "fileset":common.MapStr{"name":"log"}, "host":common.MapStr{"name":"filebeat-2gknk"}, "input":common.MapStr{"type":"docker"}, "kubernetes":common.MapStr{"container":common.MapStr{"name":"istio-proxy"}, "labels":common.MapStr{"app":"swift-client", "pod-template-hash":"2509434048", "version":"7aa2136"}, "namespace":"ratecity", "node":common.MapStr{"name":"ip-192-168-6-185.ap-southeast-2.compute.internal"}, "pod":common.MapStr{"name":"swift-client-7aa2136-694f87848d-mjbvt", "uid":"bdceb002-cae8-11e9-bbab-021865055d54"}, "replicaset":common.MapStr{"name":"swift-client-7aa2136-694f87848d"}}, "log":common.MapStr{"file":common.MapStr{"path":"/var/lib/docker/containers/776b05d3d48b320170981b60d96f1cc606417adec4b8c761f6a60ac75bb7eb0a/776b05d3d48b320170981b60d96f1cc606417adec4b8c761f6a60ac75bb7eb0a-json.log"}, "offset":214267}, "message":"[2019-08-31T00:06:20.226Z] \"- - -\" 0 - \"-\" \"-\" 37524 3059 1805 - \"-\" \"-\" \"-\" \"-\" \"162.247.242.28:443\" PassthroughCluster 192.168.31.111:51384 162.247.242.28:443 192.168.31.111:51382 -", "service":common.MapStr{"type":"envoyproxy"}, "stream":"stdout", "tags":[]string{"envoyproxy"}}, Private:file.State{Id:"", Finished:false, Fileinfo:(*os.fileStat)(0xc000ba24e0), Source:"/var/lib/docker/containers/776b05d3d48b320170981b60d96f1cc606417adec4b8c761f6a60ac75bb7eb0a/776b05d3d48b320170981b60d96f1cc606417adec4b8c761f6a60ac75bb7eb0a-json.log", Offset:214537, Timestamp:time.Time{wall:0xbf528c32e407088c, ext:40892431328, loc:(*time.Location)(0x2bcc360)}, TTL:-1, Type:"docker", Meta:map[string]string{"stream":"stdout"}, FileStateOS:file.StateOS{Inode:0x87501b3, Device:0x10301}}, TimeSeries:false}, Flags:0x1} (status=400): {"type":"mapper_parsing_exception","reason":"failed to parse field [destination.bytes] of type [long] in document with id 'uKT-5GwBS35iTgd9lkNe'. Preview of field's value: '\"-\"'","caused_by":{"type":"illegal_argument_exception","reason":"For input string: \"\"-\"\""}}

I am not able to post on the discuss channel as it is closed, so only posting here.