Hi Splunkers, I have to create some modular inputs that ingest data with REST API. Searching on doc, I found Configure Data Collection using a REST API call that explain very well basic settings working with Addon Builder. Using some APIs found on a Youtube tutorial, I developed with no problem data ingestion in a very simple scenario, which is using a GET method without authentication. On above doc, I got this message: For advanced data collection, create a modular input by writing your own Python code. Now, of course I'm not here to ask how to deploy an advanced scenario; my question is to be sure that a possible scenario I have in mind must be managed with custom Python code and cannot be managed, not totally as well, with AddonBuilder GUI. This is the possible scenario: The log sources that support API, demand a first API call. This call is a POST with username and password. The log source respond with an header that contain API Token User must then perform a GET with header enriched with above API Token. Now, in a "lazy" way, I could perform the first call on an API Client, like Postman, get the API Token and pass it to my addon Data Collection configuration, for example here: In this way, I can avoid totally Python code and use only AddonBuilder GUI. Simple, isn't it? By the way, following this method, the token is hard coded and if we need to change it, for example using a different username an password, we need to change the addon in Configure Data Collection Setting. What I want to achieve is: if a user want to install and use the addon on its own Splunk instance, with its own credentials, and he/she don't want provide the API Token but username and password, I have to implement this setting with Python code; I have no way to tell to Addon Builder "Ehy, take credentials and then the token is the one from response" ONLY with GUI. Right?
... View more