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 Delivered
Workspace API Connect
Created by Guest
Created on Jan 31, 2018

Improve analytics processing and reporting

Improve analytics processing and reporting
Sizing for larger installations
Split-brain handling for both elastic search and
main-site processors

Idea priority Urgent
RFE ID 115820
RFE URL
RFE Product IBM API Connect
  • Guest
    Reply
    |
    Feb 1, 2018

    I endorse this RFE, particularly from the standpoint of split brain self healing. Since this is an analytics-based request, the database at issue is ElasticSearch. We have seen some cases where bad shards are detected and refreshed and self-healing occurs but too many times it does not requiring mitigating action to manually heal the database - usually by restarting it. We would like something more resilient than that to small network interruptions. Our analytics access has become almost as important to us as the execution of the APIs themselves.