8 results found

1. Kafka versioned updates

   As a platform engineer
   I want the service updates to be versioned and to be able to select a specific version (Kafka, Karapace, etc) to update to so that I can perform correct change promotion from non-prod to production (instead of being forced to always apply the latest) and so that if a new version is released while an update is in-flight it would not lead to different versions running across the brokers (as is currently the case, which we have experienced can lead to incompatibilities). Additionally, I would like it to be clear what version(s) is currently running in a service and for each version to have a clear changelog

   As a platform engineer
   I want the service updates to be versioned and to be able to select a specific version (Kafka, Karapace, etc) to update to so that I can perform correct change promotion from non-prod to production (instead of being forced to always apply the latest) and so that if a new version is released while an update is in-flight it would not lead to different versions running across the brokers (as is currently the case, which we have experienced can lead to incompatibilities). Additionally, I would like it to be clear what version(s) is currently running in… more

   12 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Aiven for Apache Kafka®  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Enhance error messages and logs with schema names and versions

   As a developer,
   I want error messages and logs to contain schema names and versions,
   so that I can quickly identify and troubleshoot issues related to specific schemas more efficiently.
   In addition, this improvement is very important when dealing with issues in referenced schemas because it provides more context in error messages and logs, making it easier to diagnose and resolve problems. This can significantly reduce the time spent on debugging and improve overall system maintainability.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Karapace  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Enforce schema compatibility check on level change

   As a developer,
   I want to have an enforced compatibility check on all existing schemas when the compatibility level is set to a more restrictive one (or for any change),
   so that I can ensure all schemas comply with the new restrictive compatibility level and maintain consistency in the schema registry.
   In addition, this improvement is important because it prevents potential issues when new schemas are registered or existing ones are updated, thereby increasing the reliability of the schema registry.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Karapace  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Provide documentation for Karapace REST API

   As a developer
   I want to use a REST API against my Kafka instance
   so that I can write simple scripts without using client libraries.

   It doesn't seem like there's comprehensive API documentation for what endpoints and functionality are supported by the Karapace REST API. The website says it's a drop-in replacement for the Kafka REST API proxy but unless that comes with guarantees that it'll stay up-to-date with any changes in the Confluent Kafka REST API proxy, it's hard to trust that. Some users may find it preferable to just have the documentation for Karapace's endpoints.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Karapace  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Exactly-Once support in Storage Write API from our GBQ sink connector

   Add support for exactly-once delivery in Storage Write API for GBQ sink connector.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Aiven for Apache Kafka® Connect  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. untyped metrics from prometheus endpoint

   using prometheus endpoint at our kafka-service we need to have metrics from kafka with type .

   see below the metrics have notype - this should be set at the endpoint ,to ease the use of these metrics .
   see example

   TYPE kafkaservergroupcoordinatormetricsgroupcompletedrebalancecount untyped

   TYPE kafkaservergroupcoordinatormetricsoffsetcommit_rate untyped

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Aiven for Apache Kafka®  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. "Last Used" field on Kafka Certificates in Console/API

   As an organization (DevOps/Security/Vendor Manager) using Aiven Kafka,
   we want to determine the last connected cert status of Kafka users,
   so that we can know whether a kafka user certificate has been successfully updated.

   We automate certificate rolling to an extent with terraform. Different teams of devs generally own their section of terraform creating Kafka users. As of right now every two years those certs expire, and clicking the "Yes I've updated" in the Aiven console just silences the alert, and provides no real time verification from the running kafka that a certificate has been updated.

   This means a user with console access can accidentally or erroneously click that button that they've updated a kafka certificate without actually updating the certificate in staging/production, and no alert or reminder email will be sent, and the cert will expire, and the client will slowly start failing connections to partitions over days, costing thousands of dollars as the data transferal job fails but in a piecemeal way that wasn't easily detected by healthchecks.

   The results are just some data isn't there, depending on partition key. Currently without scanning every certificate in use by every application this scenario is not detectable on our side, but may be very easily visible if you have access to the Kafka connection logs and use that to capture for the Console on which certificates are in use.

   As an organization (DevOps/Security/Vendor Manager) using Aiven Kafka,
   we want to determine the last connected cert status of Kafka users,
   so that we can know whether a kafka user certificate has been successfully updated.

   We automate certificate rolling to an extent with terraform. Different teams of devs generally own their section of terraform creating Kafka users. As of right now every two years those certs expire, and clicking the "Yes I've updated" in the Aiven console just silences the alert, and provides no real time verification from the running kafka that a certificate has been updated.

   This means a user… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Aiven for Apache Kafka®  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Support for both allow and black lists in Kafka service

   As a managed Kafka administrator
   I want to have the ability to black-list a bunch of IP addresses I believe are suspicious from my Kafka service, so that I can prevent my service being disrupted by unexpected traffic
   In addition, I would like to keep the current allow-list to be able to allow know IPs and a way to resolve a conflict between allow and block list where block list takes priority.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Aiven for Apache Kafka®  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close