Integration release checklist

This checklist is intended for integrations maintainers to ensure consistency
when creating or updating a Package, Module or Dataset for an Integration.

All changes

• Change follows development guidelines
• Supported versions of the monitoring target are documented
• Supported operating systems are documented (if applicable)
• Integration or System tests exist
• Documentation exists
• Fields follow ECS and naming conventions
• At least a manual test with ES / Kibana / Agent has been performed.
• Required Kibana version set to:

New Package

• Screenshot of the "Add Integration" page on Fleet added

Dashboards changes

• Dashboards exists
• Screenshots added or updated
• Datastream filters added to visualizations

Log dataset changes

• Pipeline tests exist (if applicable)
• Generated output for at least 1 log file exists

Metric dataset changes

This entry is currently only recommended. It will be mandatory once we provide better support for it.

• Sample event (sample_event.json) exists

Filebeat module changes

• Test log files exist for the grok patterns
• Generated output for at least 1 log file exists

Metricbeat module changes

• Example data.json exists and an automated way to generate it exists (go test -data)
• Test environment in Docker exist for integration tests