org.apache.nifinifi-windows-event-log-nar2.3.02.0.0rel/nifi-2.3.0main1org.apache.nifi.processors.windows.event.log.ConsumeWindowsEventLogPROCESSORRegisters a Windows Event Log Subscribe Callback to receive FlowFiles from Events on Windows. These can be filtered via channel and XPath.ingesteventwindowschannelChannelThe Windows Event Log Channel to listen to.SystemtruefalsetrueENVIRONMENTfalsefalsequeryXPath QueryXPath Query to filter events. (See https://msdn.microsoft.com/en-us/library/windows/desktop/dd996910(v=vs.85).aspx for examples.)*truefalsetrueENVIRONMENTfalsefalsemaxBufferMaximum Buffer SizeThe individual Event Log XMLs are rendered to a buffer. This specifies the maximum size in bytes that the buffer will be allowed to grow to. (Limiting the maximum size of an individual Event XML.)1048576truefalsefalseNONEfalsefalsemaxQueueMaximum queue sizeEvents are received asynchronously and must be output as FlowFiles when the processor is triggered. This specifies the maximum number of events to queue for transformation into FlowFiles.1024truefalsefalseNONEfalsefalseinactiveDurationToReconnectInactive duration to reconnectIf no new event logs are processed for the specified time period, this processor will try reconnecting to recover from a state where any further messages cannot be consumed. Such situation can happen if Windows Event Log service is restarted, or ERROR_EVT_QUERY_RESULT_STALE (15011) is returned. Setting no duration, e.g. '0 ms' disables auto-reconnection.10 minstruefalsetrueENVIRONMENTfalsefalsesuccessRelationship for successfully consumed events.falsemime.typeWill set a MIME type value of application/xml.trueINPUT_FORBIDDEN