-
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
Temporary fix to get CI back to green #10516
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,5 @@ | ||
[ | ||
{ | ||
"@timestamp": "2018-06-19T05:16:15.549Z", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @ycombinator Do you know why these timestamps are removed? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is the removal of these lines needed to get CI green? If not I'd keep them out of this PR. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It is what happens when I regenerate the files. For now will remove all the module changes and skip the module tests with a follow up PR. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Those |
||
"ecs.version": "1.0.0-beta2", | ||
"elasticsearch.audit.layer": "rest", | ||
"event.dataset": "elasticsearch.audit", | ||
|
@@ -16,7 +15,6 @@ | |
"user.name": "i030648" | ||
}, | ||
{ | ||
"@timestamp": "2018-06-19T05:07:52.304Z", | ||
"ecs.version": "1.0.0-beta2", | ||
"elasticsearch.audit.layer": "rest", | ||
"elasticsearch.node.name": "v_VJhjV", | ||
|
@@ -33,7 +31,6 @@ | |
"user.name": "rado" | ||
}, | ||
{ | ||
"@timestamp": "2018-06-19T05:00:15.778Z", | ||
"ecs.version": "1.0.0-beta2", | ||
"elasticsearch.audit.action": "indices:data/read/scroll/clear", | ||
"elasticsearch.audit.layer": "transport", | ||
|
@@ -51,7 +48,6 @@ | |
"user.name": "_xpack_security" | ||
}, | ||
{ | ||
"@timestamp": "2018-06-19T05:07:45.544Z", | ||
"ecs.version": "1.0.0-beta2", | ||
"elasticsearch.audit.layer": "rest", | ||
"elasticsearch.node.name": "v_VJhjV", | ||
|
@@ -67,7 +63,6 @@ | |
"url.original": "/_xpack/security/_authenticate" | ||
}, | ||
{ | ||
"@timestamp": "2018-06-19T05:26:27.268Z", | ||
"ecs.version": "1.0.0-beta2", | ||
"elasticsearch.audit.layer": "rest", | ||
"event.dataset": "elasticsearch.audit", | ||
|
@@ -83,7 +78,6 @@ | |
"user.name": "N078801" | ||
}, | ||
{ | ||
"@timestamp": "2018-06-19T05:55:26.898Z", | ||
"ecs.version": "1.0.0-beta2", | ||
"elasticsearch.audit.action": "cluster:monitor/main", | ||
"elasticsearch.audit.layer": "transport", | ||
|
@@ -101,7 +95,6 @@ | |
"user.name": "_anonymous" | ||
}, | ||
{ | ||
"@timestamp": "2018-06-19T05:24:15.190Z", | ||
"ecs.version": "1.0.0-beta2", | ||
"elasticsearch.audit.layer": "rest", | ||
"elasticsearch.node.name": "v_VJhjV", | ||
|
@@ -119,7 +112,6 @@ | |
"user.name": "elastic" | ||
}, | ||
{ | ||
"@timestamp": "2019-01-08T14:15:02.011Z", | ||
"ecs.version": "1.0.0-beta2", | ||
"elasticsearch.audit.action": "indices:data/read/search[free_context]", | ||
"elasticsearch.audit.indices": [ | ||
|
@@ -152,7 +144,6 @@ | |
"user.name": "username" | ||
}, | ||
{ | ||
"@timestamp": "2019-01-27T20:04:27.244Z", | ||
"ecs.version": "1.0.0-beta2", | ||
"elasticsearch.audit.layer": "rest", | ||
"elasticsearch.audit.realm": "default_file", | ||
|
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.
@jsoriano @spinscale Is this change related to the date changes in Elasticsearch? The original timestamp looks as following:
[10/Aug/2018:09:45:56 +0200]
.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.
Looks like that, yes, #10433 reopened.