Watson Marketing Ideas

Use this form to submit an idea for a new product feature. The product team will review your input and provide status updates as decisions are made regarding the request.

Before you submit a new idea, please view requests that have already been submitted. If your idea has already been submitted, you can add comments or vote on the existing idea, thereby indicating your agreement with the idea. We may use this information to help prioritize development of new features.


Submit ideas for Watson Commerce and Watson Supply Chain products

Event Bus Open Source Publishing Agent - Full Data Stream Access

At present the event bus for On Premise is very limited.  The "CEP" agent has three options: File, TCP and HTTP.  However, each of these go through the same CEP transformation, taking fixed fields and mapping them to columns for output.  This means you must know all the fields that are there, in order to extract data.  But if there is other data presented, it will not be captured.

The pipeline Socket agent is proprietary, and requires a handshake to confirm delivery of data downstream, so as such 3rd party software cannot "listen" to it, without it failing to operate, as they do not know the handshake.

This request is to create a more open source agent that will allow ALL the data in the Event Bus pipeline to be real-time data available to other systems, Request and Response payload.  This would allow us to send this data to other messaging systems like Kafka, Streambase, IBM-MQ, Splunk, etc. 

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 11 2018
How will this idea be used?

Of immediate interest to security, fraud, risk and other that wish to see data and fields that people are trying to inject us with.  Headers, cookie names/values, etc.  We cannot use the Event Bus, as we don't know the fields they are using - that's the point, so we can't pre-state the fields to come out of the CEP agent.  We can't use the Archive agent as it was never updated for high-speed, and file write/read is a waste of system resources.  We need a high-speed in-memory/CPU agent to be able to send the data to a messaging system.

What is your industry? Banking
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files