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.

Sign up for GitHub

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

Jump to bottom

Metricbeat&logstash error:404 Not Found #6274

Closed
suhzh opened this issue Feb 5, 2018 · 1 comment
Closed

Metricbeat&logstash error:404 Not Found #6274

suhzh opened this issue Feb 5, 2018 · 1 comment
Labels
bug Metricbeat Metricbeat

Comments

@suhzh
Copy link

suhzh commented Feb 5, 2018

I’m using the metricbeat6.1.2 and the logstash version is 6.1.2 too! I want to get the logstash operating parameters, but I got the errors: HTTP error 404 in node: 404 Not Found and HTTP error 404 in node_stats: 404 Not Found! I would like to ask whether there is next encounter To the same mistake as me, and how did you solve?Thanks a lot! :)
@suhzh
Copy link
Author

suhzh commented Feb 5, 2018

After changing the hosts in logstash.yml, the localhost---> localhost: 9600 , this error has been amended. This point in the relevant documents and configuration files are not marked out, I was aware of logstash comes with the monitoring function, with this idea and test, the result is valid.

@ph ph added bug Metricbeat Metricbeat labels Feb 5, 2018
@ph ph mentioned this issue Feb 5, 2018
Merged
ph added a commit to ph/beats that referenced this issue Feb 5, 2018
@ph
Metricbeat, include the logstash port in the metricbeat configuration
0c2db5d 
The YAML for the Logstash module did not include the port, this was
making the module unable to retrieve stats from the logstash host.

Fixes: elastic#6274
exekias pushed a commit that referenced this issue Feb 5, 2018
@ph @exekias
Metricbeat, include the logstash port in the metricbeat configuration (…
fce12c1 
…#6279)

The YAML for the Logstash module did not include the port, this was
making the module unable to retrieve stats from the logstash host.

Fixes: #6274
@ph ph mentioned this issue Feb 5, 2018
Merged
@ph ph mentioned this issue Feb 5, 2018
Merged
ph added a commit to ph/beats that referenced this issue Feb 9, 2018
@ph
Metricbeat, include the logstash port in the metricbeat configuration (…
b71e1b9 
…elastic#6279)

The YAML for the Logstash module did not include the port, this was
making the module unable to retrieve stats from the logstash host.

Fixes: elastic#6274
(cherry picked from commit fce12c1)
ph added a commit to ph/beats that referenced this issue Feb 9, 2018
@ph
Metricbeat, include the logstash port in the metricbeat configuration (…
1bfbb78 
…elastic#6279)

The YAML for the Logstash module did not include the port, this was
making the module unable to retrieve stats from the logstash host.

Fixes: elastic#6274
(cherry picked from commit fce12c1)
ruflin pushed a commit that referenced this issue Feb 10, 2018
@ph @ruflin
Metricbeat, include the logstash port in the metricbeat configuration (…
4f246bd 
…#6279) (#6287)

The YAML for the Logstash module did not include the port, this was
making the module unable to retrieve stats from the logstash host.

Fixes: #6274
(cherry picked from commit fce12c1)
ruflin pushed a commit that referenced this issue Feb 10, 2018
@ph @ruflin
Metricbeat, include the logstash port in the metricbeat configuration (…
e81192b 
…#6279) (#6286)

The YAML for the Logstash module did not include the port, this was
making the module unable to retrieve stats from the logstash host.

Fixes: #6274
(cherry picked from commit fce12c1)
leweafan pushed a commit to leweafan/beats that referenced this issue Apr 28, 2023
@ph @ruflin
Metricbeat, include the logstash port in the metricbeat configuration (…
cdef45f 
…elastic#6279) (elastic#6287)

The YAML for the Logstash module did not include the port, this was
making the module unable to retrieve stats from the logstash host.

Fixes: elastic#6274
(cherry picked from commit d805f94)
leweafan pushed a commit to leweafan/beats that referenced this issue Apr 28, 2023
@ph @ruflin
Metricbeat, include the logstash port in the metricbeat configuration (…
b610c28 
…elastic#6279) (elastic#6286)

The YAML for the Logstash module did not include the port, this was
making the module unable to retrieve stats from the logstash host.

Fixes: elastic#6274
(cherry picked from commit d805f94)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Metricbeat Metricbeat
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ph @suhzh