Every JDBC database log source requires their own collector --> One collector per certain database configuration

Idea ID 2779974

Every JDBC database log source requires their own collector --> One collector per certain database configuration

Hi,
Currently JDBC database implementation needs a collector per single logsource. Even if the query is the same between servers. The offset value seems to be stored in collector (why?). This does not sound very inefficient.

I would like to have a single collector (it may contain the database query) and the following log source should contain the information how to make the query (IP, username,password and table) and the offset information. This way identical log sources could be duplicated easily under single collector.

-Br, TimoS
2 Comments
Absent Member.
Absent Member.
Hi Timo, This is about to be addressed in the next month or so.
Absent Member.
Absent Member.
Any news? Do you need more info regarding this?
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.