Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review log entries related to monitoring via internal collection #13298

Open
robbavey opened this issue Oct 7, 2021 · 3 comments · May be fixed by #16938
Open

Review log entries related to monitoring via internal collection #13298

robbavey opened this issue Oct 7, 2021 · 3 comments · May be fixed by #16938

Comments

@robbavey
Copy link
Member

robbavey commented Oct 7, 2021

Currently, when using monitoring in Logstash, a number of warnings and deprecation logs are emitted:

In regular logstash logs:

[2021-10-06T14:48:49,171][WARN ][logstash.outputs.elasticsearchmonitoring][.monitoring-logstash] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document _type {:es_version=>7}

and

[2021-10-06T14:48:49,343][WARN ][logstash.javapipeline    ][.monitoring-logstash] 'pipeline.ordered' is enabled and is likely less efficient, consider disabling if preserving event order is not necessary

These are not actionable by users, they are emitted regardless of settings in logstash.yml if internal collection is enabled.

Additionally, in the deprecation log:

[2021-10-06T14:40:03,729][WARN ][deprecation.logstash.monitoringextension.pipelineregisterhook] Internal collectors option for Logstash monitoring is deprecated and targeted for removal in the next major version.
Please configure Metricbeat to monitor Logstash. Documentation can be found at: 
https://www.elastic.co/guide/en/logstash/current/monitoring-with-metricbeat.html

We should ensure that this message is accurate, and reflects the reality wrt using internal collectors with Logstash with 8.0 of Elasticsearch

@yomduf
Copy link

yomduf commented Nov 29, 2022

Hi,
These deprecation logs are emitted even without monitoring enabled :
We just need to have Elasticsearch output.
Logstash 8.5->ES 8.5

input {
    generator {

        lines => [ '{"key":"value","secondkey":"secondvalue"}' ]
        count => 1
    }
}
filter {
    json {
        source => "message"
    }
}

output {
    stdout {
        codec => rubydebug {
        }
    }
        elasticsearch {
    }

}

Related warning:

{"level":"WARN","loggerName":"logstash.outputs.elasticsearch","timeMillis":1669730430179,"thread":"[inputfile.conf]-pipeline-manager","logEvent":{"message":"Detected a 6.x and above cluster: the `type` event field won't be used to determine the document _type","es_version":8}}

@robbavey
Copy link
Member Author

Created logstash-plugins/logstash-output-elasticsearch#1198 to track Elasticsearch output unnecessary output

@robbavey
Copy link
Member Author

[2021-10-06T14:48:49,171][WARN ][logstash.outputs.elasticsearchmonitoring][.monitoring-logstash] Detected a 6.x and above cluster: the type event field won't be used to determine the document _type {:es_version=>7}

should be resolved as of version 12.0.1 and 11.22.11 of the Elasticsearch output

@kaisecheng kaisecheng self-assigned this Jan 23, 2025
@kaisecheng kaisecheng linked a pull request Jan 23, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants