efe4pj wrote:

I intend to write the catched logs to a specific table in our database, so that application can re-read
the info as they like.
Do you think that to be a good solution?

Also how do you get the script for log table creation ?


Regards

If it fits your needs that is a very good solution.

The easiest way to create the log tables is to connect the tLogCatcher, tStatCatcher, and tFlowMeterCatcher components to DB outputs and change the "Action on Table" to "Drop table if exists and create"

You will need to use the tFlowMeter and have a small subjob so that rows get created and the Catcher components get data.

I dug into Stats&Logs mechanics somewhat and know I'm puzzled.

I need to use Talend in the following context:
- serverside with an Oracle DB
- clientside, without network, with a MySql DB (nomad netbook)

In addition, the nomad netbook has some other application installed, mostly .NET ones, and I need to allow then to read Talend logs, and I feel not inclined to request them to parse log files.

I isolated the Talend tables (logs, flows, stats) in a specific schema for Oracle, a specific database for MySql.

In my other jobs, I use context variable and "Run If" triggers to select the path of execution of the job.

Global logging does not allow me to select one Database Connection to write to, if and only if a context variable is set with a specific value.

Moreover, I can tell global logging to use a repository connection, but it fails if that metaconnection is "exported as context" (bug1). Workaround is I can use context variable directly is the global log settings.

But anyway, that does not solve my problem, because generated code in "talendLogs_LOGSProcess()" method is different whether I use MySql or Oracle. That means I have to distribute 2 differents binaries, serverside or clientside.

That means I must rely on one person, the "head of project development", to set TOS successively in both configuration and "export scripts", and because of bug1 above, it's not a simple combo value switching. No automation using ANT or such tools.

Well having thought about it again and again, what I really need in global logs settings is:
- support of "context variable" for File and DB outputs.
- possibility to define a list of DBOutput (in my case 2 are needed)
- have and conditional activation on every output also based on context variable

I will open an Issue for bug1 and wait for your feedback on the rest of this post.


Best regards

Good idea. I will try with the generic connection.
But I think there will be performance degradation compared to a dedicated one.

Will keep you informed.

Regards