ActiveMQ_package(#606)

[kush-crest]

What does this PR do?

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• If I'm introducing a new feature, I have modified the Kibana version constraint in my package's manifest.yml file to point to the latest Elastic stack release (e.g. ^7.13.0).

Author's Checklist

• Each data streams should contains system tests.
• Each data streams should contains sample_event.json.
• Each data streams should successfully pass all tests.

How to test this PR locally

• Clone integrations repo.
• Install elastic-package locally.
• Start elastic stack using elastic-package.
• Move to integrations/packages/activemq directory.
• Run following command to run system tests. elastic-package test system -v

Related issues

• Relates Create ActiveMQ integration #606

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-08-30T15:03:48.161+0000

• Duration: 17 min 6 sec

• Commit: b31a5c0

Test stats 🧪

Test	Results
Failed	0
Passed	52
Skipped	0
Total	52

Trends 🧪

[jsoriano]

/test

[jsoriano]

/test

[jsoriano]

/test

[jsoriano]

service.type is an ECS field, you can define it in ecs.yml as an external field. (And service.address will be in ECS 1.12 elastic/ecs#1537).