This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

New Relic on message processors

Posted on 09-13-2016 05:03 PM
Not applicable
Reply posted on --/--/---- --:-- AM

We want to put a profiler (New Relic) on one of our message processors to monitor the outbound traffic.


Is there any reason that this would be a bad idea on a message processor? Does the Apigee team have any experience with trying something like this?

1 1 235
Topic Labels
1 REPLY 1

Posted on --/--/---- --:-- AM
Not applicable
Reply posted on --/--/---- --:-- AM

We ended up trying this.

New Relic ended up instrumenting the code so we could see basic Apigee Cluster 'chatter'. We had visibility into Apigee Message processors communicating with the Management Servers and so on....

We had no visibility into the API proxy traffic, which is what we were looking for.

We did not leave New Relic installed long enough to analyze any latency impact in the Message processor.