Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

The tag "beats_input_codec_plain_applied" present in every document in Kibana

I have set up the ELK stack with the version 7.2.0 : filebeat, logstash, elasticsearch & kibana.

When I send my logs to Kibana, I can see a tag "beats_input_codec_plain_applied" in every document.

I search through internet but there is no explanation about why this tag is added.

like image 858
d3vpasha Avatar asked May 13 '20 18:05

d3vpasha


People also ask

What are beats in Kibana?

Beats are open source data shippers that you install as agents on your servers to send operational data to Elasticsearch. Elastic provides Beats for capturing: Beats can send data directly to Elasticsearch or via Logstash, where you can further process and enhance the data, before visualizing it in Kibana.

How do I monitor beats in a Kibana cluster?

If you are monitoring Beats, the Stack Monitoring page in Kibana contains a panel for Beats in the cluster overview. To view an overview of the Beats data in the cluster, click Overview. The overview page has a section for activity in the last day, which is a real-time sample of data.

Should we switch Kibana to use the correct exclude/include syntax?

While this is an issue in Elasticsearch that will be fixed, we should switch Kibana over to use the correct exclude / include syntax since this old syntax is likely going to remain removed in 6.0. We should show a deprecation notice whenever the old syntax is used. I'll create separate issues for this. Sorry, something went wrong.

What are Elasticsearch beats?

What are Beats? edit Beats are open source data shippers that you install as agents on your servers to send operational data to Elasticsearch. Elastic provides Beats for capturing: Beats can send data directly to Elasticsearch or via Logstash, where you can further process and enhance the data, before visualizing it in Kibana.


Video Answer


1 Answers

This seems to be undocumented, but this tag is added to every beats message by logstash beats input, it shows which codec was applied to the beats message, in your case it is the plain codec.

You can remove it in the logstash pipeline using a mutate filter.

mutate {
    remove_tag => ["beats_input_codec_plain_applied"]
} 

Or you can disable it in the input configuration by setting the option include_codec_tag to false.

input {
    beats {
        ... your beats input config ...
        include_codec_tag => false
    }
} 
like image 164
leandrojmp Avatar answered Oct 07 '22 12:10

leandrojmp