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

[Heartbeat] Fix null pointer in per-monitor SSL setting #26391

Closed
andrewvc opened this issue Jun 21, 2021 · 2 comments
Closed

[Heartbeat] Fix null pointer in per-monitor SSL setting #26391

andrewvc opened this issue Jun 21, 2021 · 2 comments
Assignees
Labels

Comments

@andrewvc
Copy link
Contributor

Per https://discuss.elastic.co/t/heartbeat-panic-error-using-ssl-verification-mode-none/276396 heartbeat will crash when a config does not explicitly set enabled: <value> in a nested SSL block. See the config below for example:

heartbeat.monitors:
- type: http
  enabled: true
  id: anId
  name: aName
  urls: ["https//private.fr:59862"]
  schedule: '@every 10s'
  check.response.status: 200
  ssl.verification_mode: none
  #uncommenting the line below is a workaround
  #ssl.enabled: true
@andrewvc andrewvc self-assigned this Jun 21, 2021
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 21, 2021
@jsoriano jsoriano added the Team:obs-ds-hosted-services Label for the Observability Hosted Services team label Jun 23, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/uptime (Team:Uptime)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 23, 2021
@andrewvc
Copy link
Contributor Author

Closing since this was fixed in #25219

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants