Hello Arjun,
It sounds like the following pages of the documentation might help you:
Modifying your analytics dataSample filters for modifying analytics data(These are for v10.0.1.x of API Connect analytics).
You should add the required filter configuration to the `external.offload.filter` section of your analyticscluster Custom Resource if you wish the fields to be added to the offloaded data.
If you need more detail, analytics uses LogStash filters and so the Elastic documentation is also a useful reference. For example:
Ruby filter plugin | Logstash Reference [7.17] | ElasticLet me know if you have any further questions and I'll do my best to answer.
------------------------------
Mark Taylor
------------------------------
Original Message:
Sent: Mon January 31, 2022 03:50 AM
From: Arjun Pilli
Subject: Customizing analytics data
Hi All,
We are currently offloading our API Connect gateway analytics to Elasticserch. However, we have some additional fields that need to go into analytics as these will be useful for troubleshooting.
Add the following in APIC analytics:
- Authenticated user (It currently logs in request headers as base64 encoded)
- Backend/Invoke URL
- Gateway cluster name (e.g. Internal EMEA)
- Expand Request/Response headers and latency info (so that it can be used as filters on Elastic Search)
- Same Transaction ID (Global transaction ID assigned is different between DMZ and Internal gateways correctly)
I couldn't find any specific documentation on the website on how to do this. I would be grateful if anyone has an Idea on how to achieve this or pointers to documentation.
------------------------------
Arjun Pilli
------------------------------