RabbitMQ discovery pattern bugs

[3mu]

Has anyone used the out-of-box RabbitMQ discovery patterns? I'm no Rabbit expert, but the patterns appear to have multiple faults in both logic and commands. I've fixed many issues, but not knowing how a Rabbit cluster should look in ServiceNow makes it a bit tricky.

[Art Guerrante]

I can't put it to work too. I'm geting a error in the identification section of the RabbitMQ pattern:

Application discovery using patterns failed due to lack of identification section containing an entry point of TCP or ALL.

What classifier are you using? There is no out of the box classifier that trigger the pattern. Did you created a customized one? 

Are you triggering the RabbitMQ or RabbitMQ Cluster pattern? 

[3mu]

I have a cluster of 2 servers. It now maps with a RabbitMQ Cluster for each server, which then connects to rabbit on those same servers when I use a RabbitMQ entry Point with just hostname and port:

I only changed the patterns and not the classifier, but it was a complete rebuild for the RabbitMQ Cluster Windows pattern. Amongst other things:

• The Identification Section is looking for "sbin\\", but should be "ebin"
• The JSON formatting command doesn't work - it doesn't appear in the Rabbit documentation - so that breaks a number of Identification steps.
• There must be a non-printing character in Connectivity Step 3 - I had to delete the "-q" and type it back in again.
• The amqp,(\d*), regex should be amqp(?:\/ssl)?',(\d*),"::

There are similar faults in the other Rabbit patterns. The RabbitMQ Queue pattern also points to $entry_point.name but I think that should be $parent.entry_point.queue_name, and is missing \\sbin\\ in the paths to rabbitmqctl.bat.

I've attached my current patterns They are still a bit messy and maybe not complete, but at least they draw a map!