Undocumented protocols
As an open platform, IBM® QRadar® collects and processes event data through various integration methods (protocol types). You can configure some protocol types for a particular log source type that is marked as undocumented. IBM doesn't support these undocumented protocols because they are not internally tested or documented in the DSM Configuration Guide. You are responsible for determining how to get the event data into QRadar.
Documented protocols
The DSM Configuration Guide describes how to configure log sources of a particular type, with each of the protocol types that IBM fully supports for that log source type. Any protocol type that has configuration documentation for a particular log source type is considered a documented protocol for that log source type. Documented protocols are internally tested.
Example of potential issues with undocumented protocols
For example, the JDBC protocol is the documented configuration for obtaining events from a system that stores its event data in a database. You can also collect the same event data through a third-party product and then forward it to QRadar by using the syslog protocol type. Because the syslog protocol type is undocumented, you're responsible for configuring the third-party product to retrieve the event data from the database and to send it to QRadar.
For more information, see the DSM Editor overview.