-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix starttime of metricsets on dataset endpoint for metricbeat #19975
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
f5421f7
to
cdf80f1
Compare
Pinging @elastic/integrations (Team:Integrations) |
cdf80f1
to
978ce7e
Compare
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
jenkins run the tests please |
…point for metricbeat (#20147) (cherry picked from commit 88cda01) Co-authored-by: Vijay Samuel <[email protected]>
Bug
What does this PR do?
Starttime of all metricsets on the
/dataset
endpoint is always"0001-01-01T00:00:00.000Z"
. This PR fixes that.Why is it important?
Helps better debugging.
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.