topic Monitor APIGEE on Dynatrace in Open Q&A

Monitor APIGEE on Dynatrace

sbokhari — Mon, 31 Jan 2022 09:35:45 GMT

Dears,

Currently, we are mn=onitoring all our APIs via APIGEE. Thus, i need to monitor APIGEE on Dynatrace to monitor the full stack of our services.

*Note: our APIGEE is private cloud.

So, let me know if it is possible to monitor it in the meanwhile or not?

Thank you!

Best Regards,

Re: Monitor APIGEE on Dynatrace

arnit_kashi — Tue, 01 Mar 2022 09:02:54 GMT

Hi @sbokhari ,

Did you get an answer for that?

We are looking for this capability too..

Thanks,

Arnit

Re: Monitor APIGEE on Dynatrace

sbokhari — Mon, 14 Mar 2022 19:47:43 GMT

unfortunately, not yet.

Re: Monitor APIGEE on Dynatrace

mgome — Mon, 14 Mar 2022 21:22:19 GMT

We've been monitoring our Apigee private cloud instances with Dynatrace for almost two years. We've instrumented all components, but for application monitoring the primary focus is on the routers and message processors. The routers being Nginx based are the primary view into API calls going through Apigee. The message processors are proprietary, opaque, and normally just appear as proxies in service flows. I've been trying to explore the message processors more in depth to expose more timing information around pre and post flows, but have not had much success because of their closed nature and lack of documentation.

Re: Monitor APIGEE on Dynatrace

Babar_Qayyum — Mon, 26 Dec 2022 09:32:44 GMT

Hello @mgome

Do you have any updates regarding the requirements you were looking for?

Regards,

Babar

Monitor APIGEE on Dynatrace

boeschen_greg — Wed, 12 Apr 2023 20:34:10 GMT

We have installed Dynatrace on our Apigee private cloud hardware, and get host level metrics, and service level information for the Api-router, but the message processor is an opaque service, and is not able to be instrumented. (see https://community.dynatrace.com/t5/Dynatrace-product-ideas/Improve-root-cause-analysis-with-problems-involving-Apigee/idi-p/198131)

We found that problems with back end services tended to point to the api-router service, until we turned off anomaly detection for the api-router.