[Stack Monitoring] Add missing metricbeat configuration to integrations

[klacabane]

Summary

The metricbeat modules (elasticsearch, kibana,..) allows one to specify ssl configuration (certificate_authorities, verification_mode..) and other parameters like period or scope.

Since the elastic integration spawns the metricbeat module under the hood, one should be able to set any accepted metricbeat parameters from the integration.

Implementation hints

• The parameters are defined under the integration's manifest vars block
• The parameters are then transformed into a metricbeat configuration in the data streams stream.yml.hbs file

See relevant PR that added the scope parameter: #3275

• [Elasticsearch] Added ssl configuration to ES module #4946
• [Kibana] Added ssl config support to kibana module #4912
• [Logstash] Added ssl config support to logstash module #4914
• [Beats] Added ssl config support to beats module #4916

AC

• All metricbeat parameters can be set from the integration form

[miltonhultgren]

We should also add support for API keys.

[klacabane]

Updated the issue to account for the other Stack Monitoring packages

[elasticmachine]

Package beat - 0.1.0 containing this change is available at https://epr.elastic.co/search?package=beat

[elasticmachine]

Package elasticsearch - 1.2.0-preview1 containing this change is available at https://epr.elastic.co/search?package=elasticsearch

[elasticmachine]

Package kibana - 2.2.0-preview1 containing this change is available at https://epr.elastic.co/search?package=kibana

[elasticmachine]

Package logstash - 2.2.0-preview1 containing this change is available at https://epr.elastic.co/search?package=logstash

[joshdover]

We should also add support for API keys.

Did we end up doing this? I'm not seeing in my latest pull of main

[mohamedhamed-ahmed]

We should also add support for API keys.

Did we end up doing this? I'm not seeing in my latest pull of main

Hi @joshdover
We have a ticket opened for this, but not picked up yet