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
[Celerdata] integration with CelerData #2326
[Celerdata] integration with CelerData #2326
Conversation
f53931f
to
a83816c
Compare
Test Results2 tests 2 ✅ 1m 38s ⏱️ Results for commit 27f512d. ♻️ This comment has been updated with latest results. |
2ba0375
to
04f47ea
Compare
Signed-off-by: yandongxiao <yandongxiao@starrocks.com>
04f47ea
to
88b24be
Compare
Signed-off-by: yandongxiao <dxyan06@gmail.com>
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.
Some doc feedback~
@@ -0,0 +1,543 @@ | |||
metric_name,metric_type,interval,unit_name,per_unit_name,description,orientation,integration,short_name,curated_metric |
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.
Please reformat the description as complete sentences, for example:
Job statistics.
The maximum journal ID of this frontend.
Also noting that there are missing metric descriptions in here.
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.
As we do not have documentation to fully describe these metrics, the descriptions of these metrics are missing and may not be immediately fixable at this time.
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.
The reformatting issue has been resolved.
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.
Hey, it looks like a lot of these have 11 columns instead of 10 and isn't a valid CSV file, could you please fix this?
(Validations have been improved, so future commits on this PR should catch those and report errors back to you)
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.
Yes, have Fixed it
Co-authored-by: Austin Lai <76412946+alai97@users.noreply.github.com>
Co-authored-by: Austin Lai <76412946+alai97@users.noreply.github.com>
Co-authored-by: Austin Lai <76412946+alai97@users.noreply.github.com>
Co-authored-by: Austin Lai <76412946+alai97@users.noreply.github.com>
Co-authored-by: Austin Lai <76412946+alai97@users.noreply.github.com>
Co-authored-by: Austin Lai <76412946+alai97@users.noreply.github.com>
- "source:LOGS_SOURCE" | ||
timestamp: 1712716343937 | ||
- | ||
sample: "I0328 10:22:09.303526 1066 olap_server.cpp:844] try to perform path gc by tablet!" |
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 have an issue to test this one in staging. There seems there is no date (MMdd) in this log sample, but there is an expected one in the grok parser?
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.
39003729303 for the timestamp means it is definitely wrong
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.
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.
The date (MMdd) does exist, 'I0328' includes the log level and date information.
During the deployment process of Celerdata, different components, FE/BE, will be deployed on different host machines. This type of log is from the BE component.
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.
Thank you for your solid review! I will check why the timestamp is wrong
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.
Yes you are right, I got mislead by believing the number after was just a code. But this is correct, it is just the date MMdd being parsed.
I replicated the grok parser with your sample in Datadog and indeed this is parsing the timestamp well.
We have a problem with our internal tool to generate this result in the CI. I will need to investigate. Is your integration urgent to be deployed, or if we delay for few days the time I find the issue is fine on your side?
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 can accept to wait few days. During the waiting period, Can you continue to review other parts of this PR? I don't know how long it will take to merge PR.
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 will give you an update by this week on the log part. For other files included in this PR, some other people will be in charge to review. I invite you to check with the partner team if you think some areas are still pending reviews.
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 have discussed internally with our team, and it appears that we won't be addressing this issue immediately. To avoid holding up this PR, please go ahead and remove this test for now. We plan to revisit this within a few weeks to resolve the issue and reintroduce the test.
I apologize for any inconvenience, especially after I had requested you to increase the test coverage...
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.
OK, thank you for your feedback
Signed-off-by: yandongxiao <dxyan06@gmail.com>
Signed-off-by: yandongxiao <dxyan06@gmail.com>
Signed-off-by: yandongxiao <dxyan06@gmail.com>
Signed-off-by: yandongxiao <dxyan06@gmail.com>
Signed-off-by: yandongxiao <dxyan06@gmail.com>
Co-authored-by: bgoldberg122 <ben.goldberg@datadoghq.com>
Co-authored-by: bgoldberg122 <ben.goldberg@datadoghq.com>
Co-authored-by: bgoldberg122 <ben.goldberg@datadoghq.com>
What does this PR do?
The integration work between Celerdata and Datadog has been completed.
Motivation
We want to submit an official integration.
Review checklist
no-changelog
label attachedAdditional Notes
Anything else we should know when reviewing?
This is the first version of our integrated work, mainly completing: