- 
        Couldn't load subscription status. 
- Fork 506
[Enhancement] Update categories for packages #14571
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
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.
I just reviewed the changes to "windows" package since that is the only one owned by elastic-agent-data-plane.
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.
The addition of the network_security category in packages/beaconing should work; cc @sodhikirti07
| 🚀 Benchmarks reportTo see the full report comment with  | 
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.
Without elastic/package-spec providing any description of the category meanings, there is some subjectivity to the labeling. I have brought my own assumptions to this review.
Overall looks good, it probably would be good for PMs that know these products to also have a look.
| 
 Yes, agree this should be revisited, especially if it drives decisions on how to categorise each integration | 
| @daniela-elastic should I remove latest changes then in this PR for it to be merged? | 
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 two comments to address. No need for another review though, so approved and we can discuss these two questions offline
| Resolved both of the comments (by adding requested category) | 
| @shmsr could please update your review? | 
| @elastic/obs-ux-management-team @elastic/ml-ui @elastic/obs-ds-intake-services @elastic/search-extract-and-transform @elastic/integration-experience could I get your review for this PR? | 
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.
ml-ui owned change to beaconing package categories LGTM.
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.
LGTM! @shahzad31 Not sure how to do the testing manually though. Does this look good to you?
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.
Ok for apm
| 
 | 
| 💚 Build Succeeded
 History
 | 
* update category * update according to the comments * more comments from PR * added security global category to those packages that are related to security * make all integrations having parent category * add observability to another package * introduce final comments


We are using categories of packages in telemetry and it seems that categories of packages are not reliable as I found a few of security packages not marked as such, for example
awsetc.I took advantage of LLM to update the list of categories according to the readme in each integration and using this list of available categories
I have verified it as much as I could but as it touches a lot of integrations it would be great to have more eyes on it.
Every new category has justification
p.s. I am new to the integrations development so it might be I’m missing some of the usages of categories and current changes might break something. If so - I am happy to update the PR
FYI @vglagoleva @andrewkroh