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

cloud.id and cloud.auth params incorrect #283

Open
axc274 opened this issue May 25, 2021 · 1 comment
Open

cloud.id and cloud.auth params incorrect #283

axc274 opened this issue May 25, 2021 · 1 comment

Comments

@axc274
Copy link

axc274 commented May 25, 2021

The filebeat::cloud parameter is a hash in the module that expects your cloud.id and cloud.auth credentials. However when doing so the following gets outputted to the filebeat.yml config:

Screen Shot 2021-05-25 at 4 22 55 PM

Sorry for the screenshot , I couldn't get the formatting right in this post.
The filebeat config does not recognize this configuration, it expects the cloud.id and .auth key/value pairs to be at the top-level of the config. As such it expects an outputs value as well. With Elastic cloud you are not required to specify an output if you have a cloud ID. Elastic cloud will not let you specify both an output AND a cloud id.

relevant error messages with the cloud hash are:
2021-05-25T16:12:50.267-0400 INFO instance/beat.go:280 Setup Beat: filebeat; Version: 6.8.15 2021-05-25T16:12:50.267-0400 INFO instance/beat.go:309 No outputs are defined. Please define one under the output section. 2021-05-25T16:12:50.267-0400 INFO instance/beat.go:359 filebeat stopped. 2021-05-25T16:12:50.268-0400 ERROR instance/beat.go:906 Exiting: No outputs are defined. Please define one under the output section.

If i manually remove the cloud has and just keep the id and auth section, it works as expected.

The module currently does not support a filebeat::cloud.id and filebeat::cloud.auth (or similar) in hiera

@pcfens
Copy link
Owner

pcfens commented Jul 6, 2021

Filebeat parses YAML in a way the dot notation cloud.id: foo is equivalent to

cloud:
  id: foo

Because things seem to be working when you leave out the cloud. part I think things are working as expected. Can you try defining something like

class { '::filebeat':
  cloud => {
    id   => 'id_string',
    auth => 'auth_string',
  },
}

If you're using an (e)yaml hiera backend things will look something like

filebeat::cloud:
  id: id_string
  auth: auth_string

should work.

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

No branches or pull requests

2 participants