We want to trace a request as it passes through the routers, message processors similar to what we can visualize on UI.
We are currently at
OPDK version 4.15.07.00
Hi Suresh,
This can be achieved by using the "Message Logging Policy".
Please refer to:
http://docs.apigee.com/api-services/reference/message-logging-policy
Additionally, there are quite a few threads on this topic, please search for "message logging" here in the Apigee Community.
Cheers
Thanks ohad. The article mentions about attaching a log policy to the message processor but how about on the router side? For example, we would like to capture in log if a request was successfully sent to a corresponding message processor.
Suresh,
Message logging is oriented more towards message contents rather than a message's journey across Apigee Edge components. However, there are log files associated with every component. If you wanted to understand what is happening in real-time you could use the "tail -f" command against all router and message processor logs.
Please refer to page 37 & 38 in "ApigeeEdgePrivateCloud-Install-Config-Guide.pdf" that came with your version of the OPDK. You can find the log location for every component such as:
Components |
Location |
Router |
<inst-root>/apigee4/var/log/apigee/router |
Message Processor |
<inst-root>/apigee4/var/log/apigee/message-processor |
I hope that is helpful
When a request is made, we dont see any entry in any of the router logs but we do notice a log entry on the message processor logs. What kind of messages are catpured in router logs? Is there a way to capture incoming request details at the router level?
You can also capture a trace log and process using the apigee-perf-summary project.
Admittedly this is more for building a performance model of the various policies in a process rather than understanding how the message is flowing between the service layers...
User | Count |
---|---|
7 | |
2 | |
2 | |
1 | |
1 |