# Metricbeat Module / Dataset release checklist This checklist is intended for Devs which create or update a module to make sure modules are consistent. ## Modules For a fileset to go GA, the following criterias should be met: * [x] Supported versions (of RabbitMQ) are documented * [x] Supported operating systems are documented (if applicable) * [x] System tests exist * [x] Automated checks that all fields are documented * [x] Documentation * [x] Fields follow [ECS](https://github.com/elastic/ecs) and [naming conventions](https://www.elastic.co/guide/en/beats/devguide/master/event-conventions.html) * [x] ~~Dashboards exists (if applicable)~~ * [x] ~~Kibana Home Tutorial (if applicable)~~ * [x] ~~Open issue in [EUI repo](https://github.com/elastic/eui) to add [icon for module](https://elastic.github.io/eui/#/display/icons) if not already exists.~~ * [x] ~~Open PR against Kibana repo with tutorial. Examples can be found [here](https://github.com/elastic/kibana/tree/master/src/legacy/core_plugins/kibana/server/tutorials).~~ * [x] Test log files exist for the grok patterns * [x] Generated output for at least 1 log file exists ## Filebeat module * [x] Test log files exist for the grok patterns * [x] Generated output for at least 1 log file exists
Metricbeat Module / Dataset release checklist
This checklist is intended for Devs which create or update a module to make sure modules are consistent.
Modules
For a fileset to go GA, the following criterias should be met:
Dashboards exists (if applicable)Kibana Home Tutorial (if applicable)Open issue in EUI repo to add icon for module if not already exists.Open PR against Kibana repo with tutorial. Examples can be found here.Filebeat module