-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add hierarchy for Pulsar #11971
Add hierarchy for Pulsar #11971
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we don't have a showcase about PULSAR, if you have tested it, could you add some relevant screenshots?
@CodePrometheus Please follow the above review and resolve the conflicting. |
From what I saw, your V-MQ is using IP:port which is provided by the agent plugin, meanwhile, server monitoring is using service name in k8s or something similar. You build the hierarchy rules, you need to make sure whey are aligned and the rules follow the setup. |
Due to the difficulty of building the IP:port format relationship with the Pulsar-cluster ,I suggest adjusting local hosts to accommodate the Pulsar-cluster name If Pulsar java plugin report the address name as I suppose |
It works, @peachisai You’re a genius! Very thanks~ And I have an idea, is it possible to declare an empty custom key in auto-matching-rules, such as |
Please resolve the conflicts. |
1514cc4
to
fcaeb1d
Compare
Add hierarchy for Pulsar
CHANGES
log.