Hi,

Is there any way I can disable the "delete" buttons in the Kowl UI at the places shown below (in the topics list and the messages list within a topic) ? We were planning to use KOWL as a replacement for Kafka TopicsUI only if we can disable those delete buttons.

I am using kowl to read messages, and are currently unable to read the latest messages I've tried increasing the ram, but it does not seem like it helps.

I keep running into this backend error message? what is going on?

Kowl does not support NGINX.

I added a NGINX in front of Kowl and the UI is broken, because that many static resources are absolute and not relative, according to the location configured inside the nginx.conf

I configured Kowl to be under admin/kafka path, but all the static resources are pointing to / I saw in the Frontend a configuration with %PUBLIC_URL% but it needs to be exported as a environment variable from outside of the container ( like in docker compose yml example bellow )

Example for my nginx configuration:

      location /admin/kafka/ {
           proxy_pass             http://kowl:8077/;
           proxy_redirect  / /admin/kowl/;
           
           proxy_buffering                    off;
           proxy_set_header Host              $http_host;
           proxy_set_header X-Real-IP         $remote_addr;
           proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
           proxy_set_header X-Forwarded-Proto $scheme;
       }

• The number of list elements displayed exceeds the paging setting when the webpage first loads
• Table overflow
• The filter option box does not support state storage
• Not support sorting and filtering by connector status
• Not support jumping from the connector to its tasks

I have a MSK cluster, enabled username password auth. It works fine when I have for example kafka-connect with settings like this

  kafkastore.security.protocol: "SASL_SSL",
  kafkastore.sasl.mechanism: "SCRAM-SHA-512",
  kafkastore.sasl.jaas.config: org.apache.kafka.common.security.scram.ScramLoginModule required username='alice' password='alice-secret';

But when use kowl to configure

     sasl:
       enabled: true
       username: alice
       password: alice-secret
       mechanism: SCRAM-SHA-512 

It give me the error

msg":"unable to initialize sasl","source":"kafka_client","broker":"seed 0","err":"Authentication failed during authentication due to invalid credentials with SASL mechanism SCRAM-SHA-512: SASL_AUTHENTICATION_FAILED: SASL Authentication failed."}

Users have reported via Email they are using Protobuf. It's been reported that the proto files are managed using a Git repository that contains all protos. It's also possible to use Confluent's schema registry to manage the proto files. Both should be supported. Currently it's probably more common that protos are managed in a Git repository as the support for Protobuf in the schema registry is a rather new feature.

Challenges

As of now we automatically detect the required deserializer. With protobuf there's no such thing like a magic byte which indicates that the given messages is serialized with Protobuf. Therefore we must offer users an option to choose the deserialization method and furthermore what proto the backend should use to deserialize a given message (key/value).

I was wondering if it was possible to make the max message count when consuming messages configurable? Right now it's hardcoded at 500, but we'd like to play around with higher values in some of our use cases. I was thinking have a MAX max set as part of the env vars for the backend, but then let people fiddle with that number on a case by case basis to a number at, or lower than that.

I have a problem when loading consumer group and topic -> consumer menu in frontend. I used kowl helm chart with quay.io/cloudhut/kowl:master image.

I got this error in frondend

And I got this pod log.

{"level":"error","ts":"2021-01-06T07:11:40.353Z","msg":"no partition watermark for the group's topic available","group":"XXX","topic":"XXX"} {"level":"error","ts":"2021-01-06T07:11:40.353Z","msg":"Sending REST error","topic_name":"XXX","route":"/api/topics/XXX/consumers","method":"GET","status_code":500,"remote_address":"X.X.X.X","public_error":"Could not list topic consumers for requested topic","error":"failed to get consumer group lags: no partition watermark for the group's topic available"}

How can I fix this error?

Type: TypeError

Message: Cannot read properties of null (reading 'length')

Stack (Decoded): render (components/pages/consumers/Group.Details.tsx:66:98) sum (utils/arrayExtensions.ts:102:43) sum (utils/arrayExtensions.ts:102:16) render (components/pages/consumers/Group.Details.tsx:66:74) allowStateChanges (../../src/core/action.ts:149:15) reactiveRender (../../src/observerClass.ts:134:28) Array (../../src/core/derivation.ts:177:21) isSpyEnabled (../../src/core/reaction.ts:137:23) reactiveRender (../../src/observerClass.ts:132:8)

Stack (Raw): TypeError: Cannot read properties of null (reading 'length') at https://kowl03.in.obsec.io/static/js/main.366aafe9.chunk.js:1:252151 at https://kowl03.in.obsec.io/static/js/main.366aafe9.chunk.js:1:4148 at Array.reduce () at Array.sum (https://kowl03.in.obsec.io/static/js/main.366aafe9.chunk.js:1:4117) at n.value (https://kowl03.in.obsec.io/static/js/main.366aafe9.chunk.js:1:252112) at Le (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:13359) at https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:65736 at Xe (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:19292) at e.t.track (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:23628) at n.l [as render] (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:65701)

Components:

at n (https://kowl03.in.obsec.io/static/js/main.366aafe9.chunk.js:1:251171)
at t (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:116535)
at t (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:117486)
at s (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:861432)
at h (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:862141)
at Xt
at n (https://kowl03.in.obsec.io/static/js/main.366aafe9.chunk.js:1:302928)
at main
at h (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:528946)
at a (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:528776)
at section
at https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:529206
at a (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:528776)
at l (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:62025)
at section
at https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:529206
at a (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:528776)
at t (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:116535)
at t (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:117486)
at n (https://kowl03.in.obsec.io/static/js/main.366aafe9.chunk.js:1:314272)
at n (https://kowl03.in.obsec.io/static/js/main.366aafe9.chunk.js:1:346303)
at t (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:113829)
at t (https://kowl03.in.obsec.io/static/js/2.c77d56f0.chunk.js:2:563547)

Environment: NODE_ENV : production GIT_SHA : 1177dfdcda669904b0fbfc54934dbeba322bf2af GIT_REF : v1.4.0 TIMESTAMP: 1622141499 appName : Kowl

Location: Protocol: https: Path : /groups/elastic_persistence-vpqdpaoeqxxzdvjd-activity20200513 Search : Hash :

Fixes https://github.com/cloudhut/kowl/issues/237

Fixed by removing the "/" at the beginning of all file paths and added "/" as import path to the proto parser

I am running version 5.0.4 of the schema registry, and I noticed that when I point Kowl at this registry and go to the "Schema Registry" view, the REST API times out after 25s. My hunch as to what is going on, which I can't backup with logs because I'm not sure how to see the backend logs, is that the /mode endpoint wasn't added to the schema registry until 5.2.X, and so this call fails. Would it make sense to have a N/A value for mode if the call to /mode returns a 404?

RedPanda is a very nice and feature-rich UI and has really helped our team improve our Kafka operations.

One of the few features that my team still greatly admires from Confluent's Control Center (C3) is the ability to download connector configs (as JSON or properties files) and then similarly upload connector configurations.

This is typically used for various purposes, such as backup and restore when a connector needs to be rebooted or during deployment to multiple environments with minor tweaks between the connector definitions. Consider how tedious and error-prone it would be to delete and relaunch a connector through the UI one configuration at a time.

Would be nice if this feature saw its way into RedPanda console also.

Thank you for providing this tool to the community and for all the hard work you've put into making this tool great.

Fixing #405

This is still a work in progress (need more manual and unit tests) but If you find time you can validate you are OK with the direction I am heading.

I have concerns about performance if every message end up matching with the last regex in a long list. I may add a benchmark to get an idea of the difference between regex matching vs directly matching in the map (I expect a huge difference).

@mehrdad-goudarzi commented on Tue Nov 22 2022

Version & Environment

Redpanda version: (use RELEASE-2.0 843FFF4):

What went wrong?

What should have happened instead?

How to reproduce the issue?

1. Open RedPanda UI
2. Go to a specific topic
3. Try to filter the topic using filters
4. Open the same URL at the same time in a different tab
5. click on the cross icon of created filter item

This PR adds two workflows:

1. Lint Go Code
2. Unit test Go Code

I also added a task file for formatting the Go code and I ran the format task once and submitted that in a separate commit.

Snyk has created this PR to upgrade mobx-react from 7.5.3 to 7.6.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

• The recommended version is 1 version ahead of your current version.
• The recommended version was released 21 days ago, on 2022-11-14.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade mobx from 6.6.2 to 6.7.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

• The recommended version is 1 version ahead of your current version.
• The recommended version was released 21 days ago, on 2022-11-14.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

?? View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs