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

Fix misleading message when protocol is not set #12304

Closed
dadoonet opened this issue May 27, 2019 · 2 comments
Closed

Fix misleading message when protocol is not set #12304

dadoonet opened this issue May 27, 2019 · 2 comments
Assignees
Labels
bug polish Team:obs-ds-hosted-services Label for the Observability Hosted Services team

Comments

@dadoonet
Copy link
Member

In 7.1.0, when configuring a monitor like this:

heartbeat.monitors:
- type: http
  schedule: '@every 5s'
  urls:
    - 'elasticsearch:9200'

It fails with this error message:

2019-05-27T10:52:35.556Z	ERROR	instance/beat.go:802	Exiting: could not create monitor: job err missing port in address
Exiting: could not create monitor: job err missing port in address

I found it misleading as the port is there obviously. Actually the problem is coming from the protocol which is missing. It should have been:

heartbeat.monitors:
- type: http
  schedule: '@every 5s'
  urls:
    - 'http://elasticsearch:9200'
@dadoonet dadoonet added the Team:obs-ds-hosted-services Label for the Observability Hosted Services team label May 27, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/uptime

@andrewvc
Copy link
Contributor

This was fixed in #13703

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug polish Team:obs-ds-hosted-services Label for the Observability Hosted Services team
Projects
None yet
Development

No branches or pull requests

3 participants