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.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,16 @@ All notable changes to this project will be documented in this file.
4
4
The format is based on [Keep a Changelog](http://keepachangelog.com/)
5
5
and this project adheres to [Semantic Versioning](http://semver.org/).
6
6
7
-
## [Unreleased]
7
+
## [3.2.0] 2021-06-22
8
8
### Fixed
9
9
- Trace message in Traffic-Monitor is truncated [#112](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/112)
10
10
- API-Manager User looked up at API-Manager even if external HTTP-Based AuthZ is configured [#111](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/111)
11
+
- Custom-Properties in Traffic-Details Index are not indexed as they are missing in the Index-Template [#115](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/115)
12
+
- EMT-Mode - API-Gateway-Traffic-Monitor don't show traffic when Pod is recreated [#114](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/114)
13
+
- External-HTTP Authorization - Traffic-Details in Traffic-Monitor not working [#113](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/113)
14
+
15
+
### Changed
16
+
- Custom-Properties type custom now additionally indexed with type keyword [#116](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/116)
@@ -63,32 +64,36 @@ If you are upgrading from Release 1.0.0 and encounter problems, please open an i
63
64
If Filebeat changes with a version, you must update the corresponding configuration on all your API Gateway instances. It is recommended to update Filebeat as the first component, because the Filebeat configuration version is checked by the API builder process. If it does not match, Logstash will exit with an error message.
64
65
Even if you run Filebeat as a native service, you have to copy the configuration (`filebeat/filebeat.yml`) from the release into your configuration.
65
66
66
-
The following steps illustrates an update to version 2.0.2:
67
+
The following steps illustrates an update to version 3.2.0 using the docker-compose approach:
67
68
```
68
-
wget --no-check-certificate https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v2.0.2/axway-apim-elk-v2.0.2.tar.gz -O - | tar -xvz
docker-compose -f filebeat/docker-compose.filebeat.yml up -d
74
75
```
75
76
77
+
If you have deployed the solution on a Kubernetes-Cluster using Helm read [here](helm/README.md) for more information.
78
+
76
79
### API-Builder/Logstash/Memcached
77
80
78
81
If Filebeat should be updated with one of the releases that are between the current one and the new one, then please [update Filebeat](#filebeat) in advance.
79
82
80
83
API Builder, Logstash and Memcache work as a tight unit and should be stopped, updated together if possible. Please note, that changes to Logstash do not mean that the Logstash version has changed, but that the Logstash pipeline configuration has changed. To activate these changes the new release must be used to start Logstash.
81
84
82
-
The following steps illustrates an update to version 2.0.2:
85
+
The following steps illustrates an update to version 3.2.0:
83
86
```
84
-
wget --no-check-certificate https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v2.0.2/axway-apim-elk-v2.0.2.tar.gz -O - | tar -xvz
0 commit comments