You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the first version of Beats Configuration is very limited. We have a lot of different configurations for filebeat/metricbeat/winlogbeat/heartbeat, ... including modifications to metricbeat module default configuration, SSL settings for logstash output including using our custom certs authority, ... Now the Beats Management features are unusable for us. I know the Beats Management is pretty new and some things are probably somewhere in the roadmap, but as a feedback for what we are currently missing:
Ability to configure all of the beats
Better configuration for outputs - allowing SSL conf, custom certs (paths are enough, no problem to transport them another way), ... pretty everything which is possible in standalone config
Allowing to configure everything/use every config option as in standalone, not only "selecting predefined set of default configured modules etc.". So the possibility to include arbitrary part of the configuration.
The text was updated successfully, but these errors were encountered:
Currently the first version of Beats Configuration is very limited. We have a lot of different configurations for filebeat/metricbeat/winlogbeat/heartbeat, ... including modifications to metricbeat module default configuration, SSL settings for logstash output including using our custom certs authority, ... Now the Beats Management features are unusable for us. I know the Beats Management is pretty new and some things are probably somewhere in the roadmap, but as a feedback for what we are currently missing:
The text was updated successfully, but these errors were encountered: