-
Notifications
You must be signed in to change notification settings - Fork 435
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
[microsoft_dhcp] changes/fix to set values for source and the right values for host; #… #7633
Conversation
Can some one look into this please? If i am wrong with my thoughts and the thoughts behind the merge request please let me know that. Ping @elastic/security-external-integrations |
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.
This seems reasonable. Please resolve the conflict and I will run the test build.
packages/microsoft_dhcp/data_stream/log/_dev/test/pipeline/test-log.log-expected.json
Outdated
Show resolved
Hide resolved
packages/microsoft_dhcp/data_stream/log/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
Can you also resolve the conflict in the changelog (and ensure the manifest matches the resolution). |
Is there still something to do? did i miss something? |
/test |
Please run |
i did a rebase with latest changes from main. |
/test |
2 similar comments
/test |
/test |
🌐 Coverage report
|
/test |
@xtruthx Please check that the changes that I've made match your expected semantics. To answer your question, yes, the agent adds those fields in automatically. They don't need to be added into the tests, but the pipeline does need to be robust to their absence. These are the changes that I've made. |
Thanks @efd6 . That looks great. Sorry for the stuttering in progress and thanks for the patience. In the next post I know now how to do it:) 😄 |
packages/microsoft_dhcp/data_stream/log/_dev/test/pipeline/test-log.log-expected.json
Show resolved
Hide resolved
/test |
The deconfliction needs to have an update to the manifest as well; this is an irritation with how merge conflict get resolved if you do it purely in a merge conflict editor. |
/test |
Done and sorry i forgot the manifest. Now i hope it looks good. Time hits me now. |
/test |
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.
Thanks
@xtruthx I'm just wondering whether client wouldn't be better than source; this is the terminology used in the MS documentation. |
@efd6 I first thought about putting it into the ECS object 'client'. But then I thought it might be better to use 'source' so that it is also used correctly in the SIEM/Security in the Network overview. I am not sure if the field 'client.source' is also asked. I'll have a look at it again in a moment. Additional: But yes from the terminology it would not be wrong to use 'client'. |
Thanks. |
@efd6 as it thank last
@efd6 i think that means yes please do the change and i did so. When building the integration I got the following validation error:
I think it makes sense to act accordingly and I have set the kibana version to ^8..10.0 only. I hope now the merge is possible soon |
Oh, sorry. "Thanks" was for the explanation. If source is commonly used in the rules then it makes sense to use it. But rather than more churn, I'll discuss this with others. So don't make any change on that yet.
We'd rather this wasn't done since it cuts off users. The validation error really should be noted as a warning rather than an error as it is not something that blocks the build. Please revert that line change. |
We've had a discussion; please revert the source to client change. |
This reverts commit c8ae38e.
sorry reverted |
/test |
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.
Thanks
Package microsoft_dhcp - 1.23.0 containing this change is available at https://epr.elastic.co/search?package=microsoft_dhcp |
…7630
Type of change
What does this PR do?
Explainend in #7630
Checklist
changelog.yml
file.Author's Checklist
host
complete and valid (not sure actually how they created normally)Related issues
Pinging @elastic/integrations (Team:Integrations)