Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Not under consideration
Categories Event Processing
Created by Guest
Created on May 28, 2024

Ability to filter, aggregate and summarize data in-memory within the data stream

Be able to filter, aggregate and summarize data (in-memory) within the data stream. Update (with TTL) a backend sink (in-memory) data store with the associated summarized trace and metric data.

Idea priority High
  • Admin
    Sam Kunthiparambil
    Reply
    |
    Oct 17, 2024

    Decision taken in 3iab on 16 October 2024.


    We don't have a Redis sink node as of today and as our future roadmaps stand - we don't have any future plans to build one.

    The possible workaround that we see is events come in as Kafka and then goes out to Redis via Kafka connect OR
    if in the future we build out the support for Pulsar node as requested in EVI-I-131 - then we would recommend taking the output from Pulsar as a sink and then to Redis.

    This idea will be marked as Not Under Consideration.

  • Admin
    Sam Kunthiparambil
    Reply
    |
    Sep 26, 2024

    Thank your for the idea submission. We are unable to proceed on this idea request without additional information. Unfortunately, due to internal policies we can't keep this idea open beyond a certain period of time without any further action. Hence, we are marking this as "not under consideration." However, we understand that there might have been a delay in receipt information from the client side. Feel free to reach out to me or the team once you have more information for us to proceed on and we will start our action on this idea based on the new information recieved.

    Thanks again.