[Security solution][Endpoint] Add Host Isolation related data to the endpoint generator and test data loader#100727
Conversation
…-host-isolation-to-generator
|
Pinging @elastic/security-onboarding-and-lifecycle-mgt (Team:Onboarding and Lifecycle Mgt) |
| }; | ||
| } | ||
|
|
||
| export interface EndpointActionResponse { |
There was a problem hiding this comment.
Does this already exist anywhere else? @ashokaditya maybe in your PR?
There was a problem hiding this comment.
Might exist in Ash's draft. Does not exist anywhere else yet, since we don't really know what the success structure looks like (or even failure when it comes from the endpoint).
There was a problem hiding this comment.
yeah, I was wondering that as well. Feels like the Agent should know what an error/success looks like since they are the ones writing this to es. (just by looking at the schema, I thought that if error was populated, then it "failed", else, it was "success" 🤷♂️ )
There was a problem hiding this comment.
Agent knows about the fields it writes. It does not know about the fields Endpoint writes (and vice versa).
AFAIK it treats the response given via endpoint as a total unparsed black box, wraps it with its own fields, and then passes to fleet server (where maybe more fields are written? no? who knows?).
that error field is coming from either fleet-server or agent who have a failure in their system before being able to deliver to endpoint.
pzl
left a comment
There was a problem hiding this comment.
looks good. had thoughts, but nothing big
x-pack/plugins/security_solution/common/endpoint/data_generators/base_data_generator.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/security_solution/common/endpoint/data_generators/base_data_generator.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/security_solution/common/endpoint/generate_data.ts
Outdated
Show resolved
Hide resolved
| }; | ||
| } | ||
|
|
||
| export interface EndpointActionResponse { |
There was a problem hiding this comment.
Might exist in Ash's draft. Does not exist anywhere else yet, since we don't really know what the success structure looks like (or even failure when it comes from the endpoint).
| }, | ||
| state: { | ||
| isolation: false, | ||
| isolation: isIsolated, |
There was a problem hiding this comment.
future improvement: Math.random() < 0.2 ? !isIsolated : isIsolated perhaps
…-host-isolation-to-generator
💚 Build SucceededMetrics [docs]Unknown metric groupsReferences to deprecated APIs
History
To update your PR or re-run it, just comment with: |
…endpoint generator and test data loader (elastic#100727) * Generate random isolation values for endpoint metadata * Generator for Fleet Actions * Added creation of actions to the index test data loader
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
|
This was reverted by 5dde07f. https://kibana-ci.elastic.co/job/elastic+kibana+master/14367/execution/node/449/log/ |
…endpoint generator and test data loader (elastic#100727) * Generate random isolation values for endpoint metadata * Generator for Fleet Actions * Added creation of actions to the index test data loader (cherry picked from commit 57f59bd)
…ort for Host Isolation (#100813) Re-introduces the changes from #100727 which was backed out due to a bug. Changes included: * Generate random isolation values for endpoint metadata * Generator for Fleet Actions * Added creation of actions to the index test data loader Plus: * Fix generator `randomBoolean()` to ensure it works with seeded random numbers * Update resolver snapshots due to additional call to randomizer
…ort for Host Isolation (elastic#100813) Re-introduces the changes from elastic#100727 which was backed out due to a bug. Changes included: * Generate random isolation values for endpoint metadata * Generator for Fleet Actions * Added creation of actions to the index test data loader Plus: * Fix generator `randomBoolean()` to ensure it works with seeded random numbers * Update resolver snapshots due to additional call to randomizer
…ort for Host Isolation (#100813) (#100904) Re-introduces the changes from #100727 which was backed out due to a bug. Changes included: * Generate random isolation values for endpoint metadata * Generator for Fleet Actions * Added creation of actions to the index test data loader Plus: * Fix generator `randomBoolean()` to ensure it works with seeded random numbers * Update resolver snapshots due to additional call to randomizer Co-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>
Summary
--fleetoptionLoad Data
After running the above, Actions and Action Responses would be added for each host: