Debug message improved

Author: Chris Wiechmann

README.md

@@ -964,7 +964,7 @@ Any API-Gateway version that supports the Open-Traffic event log is supported. H
 
 ### Will indexed data be deleted automatically?
 
-Yes, as of version 2.0.0, each index created in Elasticsearch is assigned an Index Lifecycle Policy ([ILM](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html)). This controls how long data is retained for each data type.
+Yes, as of version 2.0.0, each index created in Elasticsearch is assigned an Index Lifecycle Policy ([ILM](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html)). This controls how long data is retained for each data type. Learn more [here](#lifecycle-management).
 
 ### Can I use this solution for multiple stages?
 
@@ -991,6 +991,11 @@ Yes, you can run Filebeat natively instead of a Docker-Container if you prefer.
 
 In case Logstash is stopped, Filebeat cannot sent events any longer to Logstash. However, Filebeat remembers the position of the last sent events on each files and resumes at that position, when Logstash is available again. Of course, you have to make sure, files are available long enough. For instance the OpenTraffic-Event Logs are configured by default to 1GB, which is sufficient for around 30 minutes when having 300 TPS. You should increase the disk space.
 
+### What happens if Filebeat is down for a while?
+
+Filebeat stores the current position in a file and which events have already been passed on. If Filebeat is shut down cleanly and then restarted, Filebeat will pick up where it left off.
+Tests have shown that it can still be that a few events are lost.
+
 ### Can I run multiple Logstash instances?
 
 Yes, Logstash is stateless (besides what is stored is Memcache), hence you can run as many Logstash instances as you like or need. In that case you have to provide multiple Logstash instances using the parameter `LOGSTASH_HOSTS` to the Filebeat instances so that they can load balance the events.

apibuilder4elastic/custom_flow_nodes/api-builder-plugin-axway-api-management/src/actions.js

@@ -249,11 +249,11 @@ async function _getAPILocalProxies(params, options) {
 		if(localAPIConfig == undefined) {
 			return;
 		} else {
-			var proxy = await _getLocalProxy(regionProxies, apiPath, policyName, options);
+			var proxy = await _getLocalProxy(regionProxies, apiPath, policyName, 'Region', options);
 			if(proxy!=undefined) return proxy;
-			proxy = await _getLocalProxy(groupProxies, apiPath, policyName, options);
+			proxy = await _getLocalProxy(groupProxies, apiPath, policyName, 'Group', options);
 			if(proxy!=undefined) return proxy;
-			proxy = await _getLocalProxy(localProxies, apiPath, policyName, options);
+			proxy = await _getLocalProxy(localProxies, apiPath, policyName, 'General', options);
 			return proxy;
 		}
 	} else {
@@ -262,9 +262,9 @@ async function _getAPILocalProxies(params, options) {
 	}
 }
 
-async function _getLocalProxy(localProxies, apiPath, policyName, options) {
+async function _getLocalProxy(localProxies, apiPath, policyName, scope, options) {
 	if(localProxies == undefined) {
-		options.logger.warn(`No configuration found in file.`);
+		options.logger.warn(`No configuration found in file (${scope}).`);
 		return;
 	}
 	var foundProxy;