Open idglabs opened 7 months ago
Hi Ilie Thanks for your comments. We will look into this as soon as we can, as some of us are on summer vacations.
Best
Hi Ilie, Based on what you've mentioned, I understand that the main confusion lies in understanding how these 2 new variables are used by the processors process_groups_history and processors_history. Firstly, I must indicate that the lists processors_list and process_group_list should be generated manually by obtaining the IDs of the objects you wish to monitor in Splunk. Below, I am providing a dummy example to illustrate how the configuration of these variables should look like. Example of test process group and processors:
The list of IDs should be separated by a line break in both variables.
Finally, this list of IDs is used by the process groups process_groups_history and processors_history to generate queries to the API with the respective IDs. We remain attentive to any doubts. Best regards.
Hello again,
Today I've decide to update on my side the app code to 1.2.1 and to add new feature you deployed related to Status History, which seem amazing
Review: a. I'm not using the HEC method , instead I'm sending all logs to a folder and is work well , where is processed be splunk forwarder b. i'm using as well SSL authentication for API in NiFi c. I've added the 2 Processor Groups / GetHttp process_groups_history and GetHttp processors_history
where I find the list of processor_list and process_groups_list who generate this list?
Processor GenerateFlowFile under GetHTTP-processor_history , my errors at moment is with Processor InvokeHTTP which seem is not passed the ${pid} in the Remote URL for both (GetHttp process_groups_history and GetHttp processors_history) not sure where ${pid} is supposed to come from in that URL ? and as well variable ${process_group_list} from where is coming?
not understanding very well the Group Processor GetHTTP-processor_history Thank you for all support
Best regards,