IBM Cloud - Structured Ideas


This portal is to open public enhancement requests against IBM Cloud and its 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.

IBM Cloud Support Center (https://cloud.ibm.com/unifiedsupport/cases/form) – Use this site for any IBM Cloud defect or support need.

Stack Overflow (https://stackoverflow.com/questions/tagged/ibm-cloud) – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud".

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

ELK Adapter enhancement to send logs to different ELK endpoints based on Org/Space

We would like for IBM to evaluate enhancing the ELK Adapter implementation to log to multiple ELK endpoints.  We need the flexibility to send logs to the respective ELK instance (non-production applications log to a non-production ELK instance).  We would like to configure the logging destination at the space level.

  • Guest
  • Feb 16 2017
  • Delivered
  • Guest commented
    5 Dec, 2018 02:28pm

    Just released, Log Analysis w logDNA [https://www.ibm.com/blogs/bluemix/2018/11/increase-observability-ibm-log-analysis-with-logdna-is-available-today-on-ibm-cloud/] supports multiple resource groups to support logging isolation in the account. Up to 32 logDNA instances can be support per account.

  • Guest commented
    1 May, 2017 05:12pm

    Hello,

    We currently support enterprise application logging with ELK and have both production and non-production ELK environments to support that. The two environments are mirror images of each other and located in different data centers so that the non-prod environment can provide disaster recovery for the prod environment. Given ELK is our Bluemix logging solution we need the ability to log to non-prod ELK from our non-prod spaces and to production ELK from our production spaces. This is because logging in non-prod typically occurs at higher levels than prod, and, more importantly, production log data will have different retention requirements than non-prod log data.

    With the ELK adaptor’s inability to log to multiple end points we are forced to drop another infrastructure layer in between Bluemix and ELK to provide the filtering/routing necessary to ensure that log data goes to the right ELK environment. There is obviously more cost involved with the additional infrastructure, not to mention the fact that it introduces another point of failure.

    Ideally the ELK adaptor would be somewhat configurable and, at a minimum, able to route based on space name.

    Please let me know if you have any additional questions.

    Thank you!

    David E. Spotts | Manager, Technology Services | BNSF Railway | 817-352-3838

  • Guest commented
    4 Apr, 2017 08:05pm

    Another consideration is that non-prod environment is used as a load testing environment by teams resulting in abnormally large volumes of logs. So, we cannot drain the non-prod logs to Prod BNSF ELK stack as that can be risk slowing down or worst case bringing down the Production ELK stack.

  • Guest commented
    4 Apr, 2017 08:01pm

    Ananda, We do not have the separation at this time. We have been draining all Bluemix logs (all spaces, dev, non-prod and prod) to our non-prod BNSF ELK stack. However, this is a huge risk as the Production applications in Bluemix do not have the same guarantees of availability and message loss from BNSF ELK stack as other non-Bluemix applications who are using the Production ELK stack. The Production BNSF ELK stack is highly available and the non-prod BNSF ELK stack is not guaranteed to be highly available. Also, we have limitations where security zones (separate security zone for Prod vs non-Prod) do not allow Production application components to connect to non-prod components. Thanks, Runu

  • Guest commented
    4 Apr, 2017 01:31pm

    Hi Ananda, we have different ELK environments (Development, Trial, Production) that corresponds to different spaces in our Bluemix environment.  Therefore, we would like to send logs from each of the Bluemix space to the corresponding ELK environments.  At this time, Bluemix logs from all spaces are being sent to only one ELK destination/environment.  We need help to configure logs from each space to sent to the correct corresponding ELK environment.

    Thanks,

    David Nguyen 

  • Guest commented
    4 Apr, 2017 04:44am

    Hello. Thanks for adding this idea to the portal.

    Would you please add some details about why you need the log destinations emanating from a single private Bluemix environment to go to multiple destinations and configured at the space level? How do you achieve this separation today? What difficulty do you run into without this ability?

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.