Skip to content

[Endpoint]: Use common event model for determining if event is v0 or v1#60667

Merged
kqualters-elastic merged 1 commit intoelastic:masterfrom
kqualters-elastic:bug/resolver-cli-data
Mar 19, 2020
Merged

[Endpoint]: Use common event model for determining if event is v0 or v1#60667
kqualters-elastic merged 1 commit intoelastic:masterfrom
kqualters-elastic:bug/resolver-cli-data

Conversation

@kqualters-elastic
Copy link
Copy Markdown
Contributor

Summary

The resolver api was using a method for differentiating between v0 and v1 events that was not correct, which caused the api to 500 when a resolver tree had children. This changes the api to use the common event model, which makes the api function correctly.

resolver_cli_data

Checklist

@kqualters-elastic kqualters-elastic added release_note:skip Skip the PR/issue when compiling release notes Team:Endpoint Data Visibility Team managing the endpoint resolver Feature:Endpoint Elastic Endpoint feature labels Mar 19, 2020
@kqualters-elastic kqualters-elastic requested a review from a team as a code owner March 19, 2020 18:13
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/endpoint-data-visibility-team (Team:Endpoint Data Visibility)

@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/endpoint-app-team (Feature:Endpoint)

@kqualters-elastic kqualters-elastic changed the title Use common event model for determining if event is v0 or v1 [Endpoint]: Use common event model for determining if event is v0 or v1 Mar 19, 2020

export function extractEventID(event: ResolverEvent) {
if (isLegacyData(event)) {
if (isLegacyEvent(event)) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

classic Resolver switcheroo 👍

@kibanamachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@kqualters-elastic kqualters-elastic merged commit cd2d54d into elastic:master Mar 19, 2020
@kqualters-elastic kqualters-elastic deleted the bug/resolver-cli-data branch March 19, 2020 20:14
kqualters-elastic added a commit to kqualters-elastic/kibana that referenced this pull request Mar 19, 2020
kqualters-elastic added a commit to kqualters-elastic/kibana that referenced this pull request Mar 20, 2020
gmmorris added a commit to gmmorris/kibana that referenced this pull request Mar 20, 2020
…o alerting/tls-warning

* 'alerting/tls-warning' of github.com:gmmorris/kibana: (32 commits)
  [ML] Listing all categorization wizard checks (elastic#60502)
  [Upgrade Assistant] First iteration of batch reindex docs (elastic#59887)
  [SIEM] Export timeline (elastic#58368)
  [SIEM] Add support for actions and throttle in Rules (elastic#59641)
  Fix ace a11y listener (elastic#60639)
  Add addInfo toast to core notifications service (elastic#60574)
  fix test description (elastic#60638)
  [SIEM] Cypress screenshots upload to google cloud (elastic#60556)
  [canvas/shareable_runtime] sync sass loaders with kbn/optimizer (elastic#60653)
  [SIEM] Fixes Modification of ML Rules (elastic#60662)
  [SIEM] [Case] Bulk status update, add comment avatar, id => title in breadcrumbs (elastic#60410)
  [Alerting] add functional tests for index threshold alertType (elastic#60597)
  [Ingest]EMT-248: add post action request handler and resources (elastic#60581)
  Return incident's url (elastic#60617)
  [Endpoint] TEST: GET alert details - boundary test for first alert retrieval (elastic#60320)
  [ML] Transforms: Fix pivot preview table mapping. (elastic#60609)
  [Endpoint] Log random seed for sample data CLI to console (elastic#60646)
  Use common event model for determining if event is v0 or v1 (elastic#60667)
  Disables PR Project Assigner workflow
  [Reporting] Allow reports to be deleted in Management > Kibana > Reporting (elastic#60077)
  ...
@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 20, 2020
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature:Endpoint Elastic Endpoint feature release_note:skip Skip the PR/issue when compiling release notes Team:Endpoint Data Visibility Team managing the endpoint resolver v7.7.0 v8.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants