Releases: Axway-API-Management-Plus/apigateway-openlogging-elk
Version 2.0.0-RC6
Fixed a few issues with parameter default handling detected in RC5.
Version 2.0.0-RC5
Another release candidate before the final 2.0.0 release. This version is tuned for max. performance and has Metricbeat included out of the box for the stack monitoring.
Version 2.0.0-RC4
The differences to the previous release candidate are:
- Payload is now shown including Sent- and Received headers, which was not the case in RC3
- Improved documentation for external User-Authorization
Version 2.0.0-RC3
A number of small changes including quality of life improvements.
Version 2.0.0-RC2
Is using a new set of sample test certificates supporting DNS-Alternatives for AWS and Azure.
Version 2.0.0-RC1
- Custom-Properties for an API now looked up
- Index mapping now includes all configured custom properties
- Regional-Support to store data from different regions separatly
- Local API-Lookup for native API-Enrichment & Disable APIs/Events ()
- Payload-Support
- External HTTP-Based User-Authorization
- Life-Cycle-Management
- Updated API-Builder to version Dubai
- Elasticsearch configuration now managed by API-Builder project and no longer by Logstash
- Index-Templates
- ILM-Policies has been added
- Rollup-Jobs has been added
See the complete changelog:
https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/blob/develop/CHANGELOG.md
Version 1.0.0
Initial release
This solution provides an out-of-the-box integration with Elasticsearch:
- Improve traffic monitor performance
- Restricted view for API Manager users on their organization
- Analytics capabilities with Kibana dashboards
- Example dashboards are included
- Ready for production use
- highly available Elasticsearch Multi-Node
- Scaling through expansion of the Elasticsearch Cluster
- Optimized for millions of transactions per day
- Connection of different data centers
- Easy deployment
- with existing Elasticsearch Cluster or via Docker-Container
- supports EMT or Classic-Deployment
- a single configuration file
- Upgradeable
Let us know your feedback, ideas, issues here on GitHub:
https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues
Version 1.0.0-RC4
This is a Release-Candidate - One more
This release provides the following changes compared to RC3:
- Changed from Elastic-Stack 7.9.0 to 7.9.2
- simplified setup of Multi-Node Elasticsearch cluster
- fixed an issue with Multi-Nodes and Kibana
Let us know your feedback, ideas, issues here on GitHub:
https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues
Version 1.0.0-RC3
This is a Release-Candidate - Hopefully the last before version 1.0.0
This release provides the following changes compared to RC2:
- added support to built a production Elasticsearch cluster with multiple nodes
- prepared up to three Elasticsearch nodes
- added support to configure multiple Elasticsearch nodes
- Domain-Audit log are index as well
- Added the option to call the API-Builder Traffic-Monitor API with an HTTP-Basic header
- Added versions to Index-Templates and Filebeat config to better support updates
- Release package now contains a folder incl. the version number
- A number of bugfixes
Let us know your feedback, ideas, issues here on GitHub:
https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues
Version 1.0.0-RC2
This is a Release-Candidate - That means, updates on this version are still not supported until version 1.0.0 is finally released.
This release provides the following changes compared to RC1:
- fixed an issue causing OPTIONS request not to show up in the Traffic-Monitor
- changed API-Builder service-name from elk-traffic-monitor-api to apibuilder4elastic
- timezone issue fixed, when parsing Trace-Messages from an API-Gateway running in a different timezone than Logstash
- slightly improved the provided Kibana dashboards
- fixed an issues in API-Builder project occurred due to concurrent requests:
- the following error message was logged in Logstash: "Cannot read property 'length' of undefined" and "Cannot read property 'type' of undefined"
- Logstash processing changed
- Trace-Messages for a selected API-Requests are indented as in the original view
- APIs without having a version now using N/A as a default
- Now Transaction-Element finalStatus is primarily used to store the transaction status
- used for instance to aggregate on the final API-Status (Pass, Fail, Error)
- for events not having a finalStatus the HTTP-Return code is used (200-299): Pass, (Others): Fail
- Exception handling added
- Filebeat now using a Docker volume to store processing data
- this makes sure, Filebeat restarts at the position it left off (even if the container is removed)
- this avoid that data is inserted twice into Elasticsearch
Let us know your feedback, ideas, issues here on GitHub:
https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues