-
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
[Feature] Instrument banyand server #9048
Comments
@kezhenxu94 @Superskyyy @remGigo Let's continue the discussion here. My suggestion is either we make this task on go2sky purely or go2sky + banyandb instrumentation (advanced one). |
We could do this, adding meter feature to go2sky is definitely a big 👍 . But why we have to couple BanyanDB and go2sky. I mean:
SO there is no dependency between go2sky and BanyanDB |
We don't choose Prometheus for now to BanyanDB. We had a discussion before. OTEL fetcher already causes many concerns. |
Quoted #9047 (comment) So, there is no concern here. |
Ok, so to sum up, an OSPP project depends on 2 non-OSPP tasks. #9047 depends on this issue to finish the task 👇
But this issue depends on go2sky to provide meter feature... |
The basic observability APIs are ready for CLI to access. They are based on Prometheus exporter go libs. The relevant feats in this thread could be based on them. |
I'd like to know where I need to bury the dots and what configuration format I need to render in yaml in order to keep track of the relevant details |
I guess "bury the dots" means what kind of operations and information we should collect or record?
I suppose according to Hongtao's comment #9048 (comment) above, Prom's text-based format is enough now. |
@lujiajing1126 I will first track the relevant process of BanYanDB. Be familiar with the general process. In order to collect information such as memory, file system and the internal state of each module |
Hello everyone, by tracking the code of skywalking-banyandb stress test. I tracked that in the KV class, statistics can be passed through dbOpts Some storage metrics of banyandb, code location @hanahmily Can you give me some advice? |
In addition, I think the indicators should be aggregated here. It is only necessary to report the indicators to the OAP backend of skywalking based on go2sky. See code location |
I don't think go2sky has meter APIs for now. Besides all instrument works, you should begin to discuss those APIs at the go2sky repo with project leader @arugal and other members. |
Ok, I am investigating the feasibility of adapting the go2sky api to the meter api. After sorting out the plan, I will communicate with the relevant maintainers in the go2sky project in the form of google doc |
@complone Hi, since the go2sky meter api is undertaken by a student through OSPP please try communicate with the mentor first so to prevent collision. |
ok thanks for letting me know |
I'm connecting with the student to confirm some details, will update to you. Update: the student will discuss the matter with mentor and update here. |
The BanyanDB server has implemented the meter module. |
Search before asking
Description
Add a series of metrics to the banyand server to measure the internal status of memory, file system, and individual modules. Furthermore, the SkyWalking OAP server could collect them to analyze, and UI could render them.
Use case
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: