rmq_tracing plugin is not working and gives a 500 error. about cf-rabbitmq-release

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

This is a RMQ clustering setup with 2 RMQ nodes.

[michaelklishin]

That plugin writes files to a local file system and in your case encounters an EACCESS.

[michaelklishin]

Since rabbitmq-tracing is nothing more than a trivial consumers and logger/UI for RabbitMQ firehose, I'd question its usefulness in environments such as PCF. Use a small app that consumes traces and is deployed to CF instead.

[michaelklishin]

Lastly, rabbitmq_tracing.directory can be used to override trace logs directory location.

Hey Mike, thanks for taking a look.

Yes, we are trying to debug an issue with p. RMq and hence we want to enable tracing temporarily.
Is there a way at all to enable tracing. For now all we did was enabled rabbit_tracing property under the plugins section. Should there be any other properties added under jobs for the tracing plugins to work.

I'd appreciate if you give us pointers or share a sample manifest. We don't want to take the sample app route to capture trace at this point of time and would want to leverage enabling the plugins through bosh release.

Thanks

[michaelklishin]

@guruprakashs please see the comments above.

@michaelklishin : Thanks for the pointer. Based on your comment we thought rabbitmq_tracing.directory to be a property under properties section of rmq-server section. But later we figured out that the following section in the manifest is to be added for the tracing plugin to work.

properties:
    rabbitmq-server:
    config: <%= ["[{rabbitmq_tracing, [{directory, "/my/log/file/location"},{username,  "guest"}]}]. "]%>