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

Elastic Stack Logstash
1

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?

2 
grok { match => { "message" => "%{COMBINEDAPACHELOG}" } }

produces a field called agent for me, containing the final quoted string. What do your log file entries look like?

3

the nginx logs

4

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