-
Notifications
You must be signed in to change notification settings - Fork 457
[ML] Not for production - Add example Transform package with new specifications for testing of new installation mechanism #4138
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
Conversation
💔 Build Failed
Expand to view the summary
Build stats
Steps errors
Expand to view the steps failures
|
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.
Left a couple of minor comments to consider – mostly nits.
unique_key: | ||
- elastic.agent.id | ||
sort: "@timestamp" | ||
description: Latest Endpoint metadata document per host |
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.
description: Latest Endpoint metadata document per host | |
description: Latest endpoint metadata document per host. |
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.
Updated here 6f89697
agent.id: | ||
terms: | ||
field: agent.id | ||
description: Merges latest Endpoint and Agent metadata documents |
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.
description: Merges latest Endpoint and Agent metadata documents | |
description: Merges latest endpoint and Agent metadata documents |
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.
Updated here 6f89697
packages/transform/manifest.yml
Outdated
source: | ||
license: "Elastic-2.0" | ||
license: basic | ||
description: "Installs and optionally starts multiple example transform tasks" |
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.
If it's the description to use on one of the tiles on the Browse integrations
page. Then I suggest the following changes so the description will be in line with the rest of the integration descriptions. (Even though the descriptions are not entirely consistent throughout the page.)
If it'll be used somewhere else, please ignore my comment.
description: "Installs and optionally starts multiple example transform tasks" | |
description: "Install and optionally start multiple example transform tasks." |
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.
Updated here 6f89697
"@timestamp": | ||
gt: now-90d/d | ||
dest: | ||
index: metrics-endpoint.metadata_current_default |
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.
It's interesting that default
is hardcoded here. While running through installation end-to-end I noticed that the Integrations UI lets you customise the "namespace" for the package. The "namespace" is "default" by default. But presumably if you change it then it changes the names of some of the assets installed by the package. So maybe we should change default
here in that case as well, to match the chosen namespace.
In general (not just for transforms) it might not be very well thought through how "namespace" influences what gets created when a package is installed.
As a companion to elastic/kibana#140046 an example transform package is being created in elastic/integrations#4138. Initially the intention was that this example would use the Kibana sample data. Then, after realising that wouldn't work due to lack of permissions, it was changed to reinstall a transform that is created by the security solution. However, it has been pointed out that this is dangerous because even if we tell people not to install the example in production it could somehow happen by mistake and then we'd have created objects that clash with production code. Therefore, it is best that the example transform package be switched back to the original idea of using the Kibana sample data, so that there is no risk of it ever clashing with a production package.
As a companion to elastic/kibana#140046 an example transform package is being created in elastic/integrations#4138. Initially the intention was that this example would use the Kibana sample data. Then, after realising that wouldn't work due to lack of permissions, it was changed to reinstall a transform that is created by the security solution. However, it has been pointed out that this is dangerous because even if we tell people not to install the example in production it could somehow happen by mistake and then we'd have created objects that clash with production code. Therefore, it is best that the example transform package be switched back to the original idea of using the Kibana sample data, so that there is no risk of it ever clashing with a production package.
c53e261
to
2ff2793
Compare
@droberts195 I've updated this package to use the Kibana sample ecommerce dataset now that elastic/elasticsearch#90037 is merged. The examples include a pivot and a latest transform. |
Thanks @qn895. The idea of using the Kibana sample ecommerce dataset and having separate pivot and latest transforms looks good to me. The details of the schema might need changing based on comments others are adding to elastic/kibana#140046. But I think the overall approach of creating an example that cannot possibly interfere with production transforms if end users install it is correct. |
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution! |
What does this PR do?
This PR is not intended for production. It simply showcases a new example package containing several transforms with specifications using the new specs elastic/package-spec#307 for testing purposes.
To get the package up and running in a test registry:
https://github.com/elastic/elastic-package
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots