You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 14, 2022. It is now read-only.
The solution supports custom properties by default which are configured in the API Manager for APIs. This means that the custom properties are indexed in Elasticsearch and can be used for customer-specific evaluations.
697
+
Since version 4.3.0, it is also possible to index runtime properties, i.e. policy attributes, in Elasticsearch and then analyze them in Kibana, for example.
698
+
699
+
The following steps are necessary:
700
+
701
+
#### 1. Export the custom attributes
702
+
703
+
In Policy Studio, configure which attributes should be exported to the transaction event log. [Learn more](https://docs.axway.com/bundle/axway-open-docs/page/docs/apim_reference/log_global_settings/index.html#transaction-event-log-settings) how to configure messages attributes to be stored in transaction events.
704
+
All exported attributes will be found in the Elasticsearch indices: `apigw-traffic-summary` & `apigw-hourly-traffic-summary` within the field: customMsgAtts.
705
+
706
+
#### 2. Configure custom properties
707
+
708
+
In order to be able to use your attributes in aggregations for reports later on, you have to configure them for the solution in advance.
709
+
By using the parameter: `EVENTLOG_CUSTOM_ATTR` you define which attributes should be indexed in Elasticsearch.
710
+
It is important that the fields have as high cardinality as possible to work efficiently in aggregations. The fields are indexed as a keyword in Elasticsearch. It is also possible to index fields as text, but these are not available in the long-term data and not recommended.
711
+
712
+
After restarting APIBuilder4Elastic, the solution will configure Elasticsearch (index templates & transform job) according to the parameter: `EVENTLOG_CUSTOM_ATTR`.
713
+
Please note that it takes 4 hours for the custom properties to be available in the transformed data (`apigw-hourly-traffic-summary`).
0 commit comments