Spotfire Ideas Portal
| Implemented in | 12.0 |
Hi,
I'm reviewing old ideas and I found this one...
As previous comments here, you can do this by configuring log4j or log4net to forward the logs to diverse destinations (see https://logging.apache.org/log4j/2.x/manual/appenders.html).
As an alternative method, you can use Cloud Deployment Kit for TIBCO Spotfire recipes, which already includes configuration for a Fluentd pod that can be used to forward the logs to the storage of your choice (see https://www.fluentd.org/dataoutputs).
Thanks
We are yet to test this but in 7.9 Spotfire moved to Log4j2 so Log4j2 DB appenders should be stable now.
https://docs.tibco.com/pub/spotfire_server/7.9.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-9DCDD9E3-7072-450E-851A-8DBAEF30598A.html
Yes, it is the same version in 7.6
Spotfire 6.5 (log4j v1.2.17) with a JDBCAppender running for a couple of days now without any noticeable issues. Btw, anyone can confirm the log4j version in 7.6? We have not yet upgraded our test environment to 7.6, but I'm guessing it's the same 1.2.17 as with 7.5?
log4j supports a JDBCAppender to log entries directly to a relational database, but the last time we were testing this was in Spotfire v4.5 (log4j v1.2.13) and every once in a while it caused a memory leak. Spotfire v6.5 and 7.5 uses log4j v1.2.17 - this version has a fix related to the JDBCAppender (https://logging.apache.org/log4j/1.2/changes-report.html#a1.2.17), but we yet to tests whether it works fine now. If it works then it's a viable solution for logging TSS logs directly to a database