Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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 Instana
Categories Self Hosted
Created by Guest
Created on Apr 18, 2022

Configurable ReplicaFactor for Kafka and Replica/Sharding for ElasticSearch in K8s Operator

customer has deployed instana in production environment, has deployed instana agents on several hundreds K8S nodes. the customer IT department is heavily using instana as their observability platform

Architecture of Instana Deployment:

the instana backend is deployed following Installing an operator-based Instana setup and the datastores are deployed on multiple VMs out of the K8S cluster for the purpose of performance and high availability.

Feature Requests:

  1. customer is using 2 nodes for kafka cluster. but instana operator will setup the kafka topic with 1 ReplicaFactor. The whole cluster will be unavailable if any single node is failure. It's better to set the parameter to more than 1 for high availability.

  2. customer is using 3 nodes for elastic cluster. but instana will setup the elasticsearch index with 1 Replicas and 1 Shards but, the whole cluster will be unavailable if any single node is failure.

please make these parameters configurable

Idea priority High
  • Admin
    Hubert Hesse
    Reply
    |
    Sep 14, 2022

    Configurable Replicas/Sharding for Elastic and ReplicaFactor for Kafka were released in 229-1. See release notes here https://www.ibm.com/docs/en/instana-observability/current?topic=operator-build-229#229-1

    the object ElasticsearchConfig has

    defaultIndexShards integer
    defaultIndexReplicas integer

    and the object KafkaConfig has

    replicationFactor integer

    now. I hope this satisfies your request. I will mark this Idea as delivered.
    Looking forward to your feedback.

  • Admin
    Hubert Hesse
    Reply
    |
    Sep 14, 2022

    Hi Jun Tan,

    configurable Replicas/Sharding for Elastic and ReplicaFactor for Kafka was released in 229-1. See release notes here https://www.ibm.com/docs/en/instana-observability/current?topic=operator-build-229#229-1

    I hope this satisfies your request. I will mark this Idea as delivered.

  • Admin
    Hubert Hesse
    Reply
    |
    Jul 6, 2022

    Hi Jun Tan,

    is this currently still an issue for you? Internally, the team has made progress with Operator based setup. Could you archive what you needed for 1 and 2 with an operator config of your choosing?

  • Admin
    Hubert Hesse
    Reply
    |
    Apr 21, 2022

    Hi Jun Tan, let me clarify those statements and requirements with the team and come back to you.

    In your related Zendesk request https://instana.zendesk.com/agent/tickets/26102 you pointed to code that, to my understanding, is used to spin up Single-Host datastore containers. If your customer created their own elastic/kafka cluster, those should not have an effect. But let me verify with the team.