Then in Central Management you create tags and create the output configuration with this tag. The output config pane includes an editor for adding custom settings.
Pipeline: you need to have the pipeline preinstalled in your cluster. Just add pipeline: metricbeat_enrich to the custom editor
Protocol: you can use the custom setting. But better configure the host to be https://5.5.5.5. In this case the protocol setting will be ignored.
SSL: you can configure the ssl settings in the custom editor. But the certificates and key file must be available on the machine the beat is running on.
Configure xpack.monitoring: This is currently not possible. You have to keep it enabled
set a keystore value for es_psw. The keystore must be available local on the machine. You will have to prepare and install the keystore similar to your certificates. This is currently not possible via Central Management.
To do this is something not currently supported for output configs in Beats CM. We are evaluating options to enable a feature like this, and look forward to supporting it in a future release
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.