In the deployed instances, CIS does indeed capture a few outgoing HTTP requests (to other APM tracked services), but the majority of them are not captured (including all to the API).The same missing trace entry behavior also occurs if I run CIS locally, hitting the deployed version of CIS API.Why are not all outgoing HTTP requests from CIS being captured?.Why are my Traces showing as incomplete in Kibana, despite having correlated entries with the same trace.id?. No event record exists for the outgoing HTTP request event from CIS to the CIS API (record 'B' from above) There are entry records being captured for the CIS API incoming request and database operation (records 'C' and 'D' from above)ī. Querying the Logs for records with the same trace.id as in the above record, however:Ī. The Trace only shows a single entry from CIS ('A' from above) Once deploying the same code to the server (running IIS), however, a few things happen: B) Outgoing HTTP request from CIS to CIS APIĭ) Database operation performed by the API
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |