Support for Artemis version of ActiveMQ.

harnish-elastic commented 10 months ago

Currently, Elastic integration only supports ActiveMQ Classic. Need to analyze ActiveMQ Artemis and check whether we can support Artemis in the current integration itself!

lalit-satapathy commented 10 months ago

Any updates here?

harnish-elastic commented 10 months ago

@lalit-satapathy, I have performed analysis on ActiveMQ Artemis,

Metrics

I have found 3 important Mbeans for the metrics data that can give us metrics.

Mbean 1: org.apache.activemq.artemis:broker=* Mbean 2: org.apache.activemq.artemis:broker=*,component=*,address=* Mbean 3: org.apache.activemq.artemis:broker=*,component=*,address=*,subcomponent=*,routing-type=*,queue=*

However, the existing integration (classic version) has different metrics from the Artemis version.

I also, performed metrics data collection with the existing activemq module. However, I can see 2-3 metrics from each data stream that are being collected by only changing mbeans from the Artemis instance!

Logs

Log patterns are different from the classic version. Please refer the below examples.

Classic audit logs example:

INFO  | guest requested /admin/purgeDestination.action [JMSDestination='test' JMSDestinationType='queue' secret='eff6a932-1b58-45da-a64a-1b30b246cfc9' ] from 127.0.0.1 | qtp12205619-36

Artemis audit logs example:

2023-12-20 15:04:58,681 [AUDIT](qtp1238568047-69) AMQ601135: User admin(amq)@0.0.0.0:51209 is listing network topology on target resource: ActiveMQServerImpl::name=0.0.0.0

Currently working on preparing the analysis doc.

muthu-mps commented 10 months ago

@lalit-satapathy, I have performed analysis on ActiveMQ Artemis,

Metrics

I have found 3 important Mbeans for the metrics data that can give us metrics.

Mbean 1: org.apache.activemq.artemis:broker=* Mbean 2: org.apache.activemq.artemis:broker=*,component=*,address=* Mbean 3: org.apache.activemq.artemis:broker=*,component=*,address=*,subcomponent=*,routing-type=*,queue=*

However, the existing integration (classic version) has different metrics from the Artemis version.

I also, performed metrics data collection with the existing activemq module. However, I can see 2-3 metrics from each data stream that are being collected by only changing mbeans from the Artemis instance!

Logs

Log patterns are different from the classic version. Please refer the below examples.

Classic audit logs example:
INFO  | guest requested /admin/purgeDestination.action [JMSDestination='test' JMSDestinationType='queue' secret='eff6a932-1b58-45da-a64a-1b30b246cfc9' ] from 127.0.0.1 | qtp12205619-36
Artemis audit logs example:
2023-12-20 15:04:58,681 [AUDIT](qtp1238568047-69) AMQ601135: User admin(amq)@0.0.0.0:51209 is listing network topology on target resource: ActiveMQServerImpl::name=0.0.0.0
Currently working on preparing the analysis doc.

@harnish-elastic - Thanks for the analysis!

muthu-mps commented 10 months ago

Observations

The data generated from the Classic and the Artemis version of ActiveMQ is not similar.
ActiveMQ relies on the native beats for data collection. Because of this there is a tight dependency to edit the beats module to process the Artemis data. Reusing of the current integration to process both the data is not possible.
Can we process data using jolokia module ?
- By using the Jolokia input module the ActiveMQ data can be processed. Further testing will be done on this.
- While looking into the Jolokia module the config test for the ActiveMQ Classic and Artemis version is already included.
  Next steps
Make the ActiveMQ(classic) integration GA.
Issue will be created to track ActiveMQ Artemis support. This will use the Jolokia module instead of ActiveMQ module.

elastic / integrations