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 Future consideration
Workspace App Connect
Created by Guest
Created on Nov 17, 2023

ACE batch ELK events and send them asynchronously from the flow transaction when the unit of work (UOW) is independent

ACE Message flow execution won't affected when ELK is down

Idea priority Medium
  • Admin
    Ben Thompson
    Reply
    |
    May 20, 2024

    Idea Review. Thank you for taking the time to raise this enhancement request. The core idea of sending data on a separate thread asynchronous to the flow transaction is similar in scope to the approach we take with flow statistics, but have not yet applied to transmission over ELK. A global configuration option could be added to either "batch" or "not batch" and we feel this external might well be the best and simplest way to implement and explain to the user (as opposed to linking the concept to the message flow transaction). Status updated to Future Consideration.

1 MERGED

ACE batch ELK events and send them asynchronously from the flow transaction when the unit of work (UOW) is independent

Merged
ACE Message flow execution won't affected when ELK is down
7 months ago in App Connect 0 Future consideration