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

Use Elasticsearch as a central config store for beats - Phase 1 #464

Closed
tbragin opened this issue Dec 7, 2015 · 3 comments
Closed

Use Elasticsearch as a central config store for beats - Phase 1 #464

tbragin opened this issue Dec 7, 2015 · 3 comments
Labels
enhancement libbeat meta

Comments

@tbragin
Copy link
Contributor

tbragin commented Dec 7, 2015

Migrated from: https://github.com/elastic/libbeat/issues/200
@ruflin ruflin mentioned this issue Dec 27, 2015
Closed
@ruflin ruflin mentioned this issue Dec 31, 2015
Merged
ruflin added a commit to ruflin/beats that referenced this issue Dec 31, 2015
@ruflin
Introduce UUID for Beat to uniquely identify each beat
e2d7755 
This is a required for centralised configuration management. See elastic#464
For the UUID id the goal is follow rfc4122 standrard: http://www.ietf.org/rfc/rfc4122.txt
@ruflin ruflin added the meta label May 30, 2016
@ruflin ruflin mentioned this issue Aug 3, 2016
Closed
@ruflin ruflin mentioned this issue Nov 21, 2016
Closed
@friesoft
Copy link

Any news on centralized configuration for beats through Kibana? We really want this feature :)

@jakauppila
Copy link

It's been a few months; curious if there's any update on this?

@ph
Copy link
Contributor

ph commented Jan 10, 2018

@jakauppila We are still planning to do it, no timeline yet.

@elasticmachine elasticmachine mentioned this issue Apr 24, 2018
Closed
9 tasks
@urso urso closed this as completed Dec 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement libbeat meta
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@ph @urso @friesoft @ruflin @tbragin @jakauppila @brandonmensing