Skip to content
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.

[BUG] No metric report to prometheus when produce/consume messages from/to pulsar using kop #152

Open
hangc0276 opened this issue May 18, 2020 · 1 comment
Open

[BUG] No metric report to prometheus when produce/consume messages from/to pulsar using kop #152

hangc0276 opened this issue May 18, 2020 · 1 comment
Labels
triage/week-21 type/bug workflow::backlog

Comments

@hangc0276
Copy link
Collaborator

Bug description

When i use kafka client produce/consume messages from/to pulsar using kop, I found two confused points:

  1. there are no message in / out metrics report to prometheus
  2. the messages' offset the consumer consumed are not continuous

It is hard to monitor the consumer lag and the message publish rate.
@jiazhai
Copy link
Contributor

jiazhai commented May 20, 2020

thanks @hangc0276 We could consider add this metrics. Currently pulsar do these metrics in producer and consumer, but kop not have a map between client producer/consumer and broker side producer/consumer.

Demogorgon314 pushed a commit to Demogorgon314/kop that referenced this issue Oct 30, 2023
@gaoran10
Add authorization check for schema registry when disabling multi-tena…
860e7d5 
…nt metadata (streamnative#152)

### Modifications

Add authorization check for schema registry when disabling multi-tenant
metadata.

### Verifying this change

Add grant and revoke permission test.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
triage/week-21 type/bug workflow::backlog
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hangc0276 @jiazhai