Hi Any idea why there's no "agent" field available once used %{COMBINEDAPACHELOG} in ELK Stack 7.1? Since what to use useragent: useragent { source => "agent" } Any idea how?

Why there's no agent field available once used %{COMBINEDAPACHELOG} in ELK Stack 7.1

system (system) Closed July 19, 2019, 5:36am 4

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

Topic		Replies	Views
Filter HTTPD_COMBINEDLOG does not display QS:agent field in Kibana Logstash	2	289	November 3, 2020
Logstash does not parse agent from NGINX access logs as it already has filebeat agent information in agent Logstash	1	403	March 17, 2020
Want a Logstash Filter to Parse the Agent Field in Apache Access Log Files Logstash	6	6950	July 6, 2017
Logstash cannot parse user_agent field of nginx Logstash	4	469	August 15, 2022
Logstash grok pattern COMBINEDAPACHELOG field name collision with latest filebeat 7.2.0 client and logstash useragent plugin Beats filebeat	5	2604	August 26, 2019