URL Logger how to trigger ETL

Thank you for the clarification

I assume that you want to insert the data into your own database or you still want to create CSV files?

I would prefer options
1. Run ETL with entry from URL-Logger
2. Add to database of choice (but I was under impression I can already define this from connection type)
3. Maybe run python on the the received data , I know I can run the same with ETL too but options are nice to have.
4. Create CSV file with ETL

An actual workflow

URL logger get a incoming request
Requested forwarded to chatGPT for summarisation
Summarised request sent to CRM

As requested we have added support for custom script execution



This script will execute aetl package 
const execFileSync = require('child_process').execFileSync;
try {
// This script might hung so always specify a timeout
const fileToExecute = '"C:\\Program Files (x86)\\DB Software Laboratory\\Advanced ETL Processor Enterprise\\aetlcl.exe"'
const objectId = 6687;
const parameters = [objectId];
const timeout = 60; //seconds
const stdout = execFileSync(fileToExecute, parameters, { shell: true, timeout: timeout*1000 });
} catch (e) {
logger.error(e.message);
return 500;
}
return 200;

PS there is no need need to uninstall the url logger, just install new version on top

Peter.Jonson wrote:

As requested we have added support for custom script execution


 

AWESOME, this saves me the step of writing a SQL trigger . If parameter passed here ObjectId here which is used the run the ETL command line from WIKI,


How do I access the JSON object
1. in ETL ,by asking it read from the sql table new object created ? 
2. in external program say non-ETL , python script , by asking it to read from the sql table ?

In both case , JSON object or the incoming request is not being passed to the ETL or program 

You can pass logId to aetl or python program 
Than you can use it to read record from the sql table

FYI: This script will print all objects available.

logger.debug(logId);
logger.debug(method);
logger.debug(originalUrl);
logger.debug(JSON.stringify(body, null, 4));
logger.debug(JSON.stringify(headers, null, 4));

return 200;