Add missing field definitions for the SQLServer integration - #6264
Conversation
34847a5 to
c5283d7
Compare
🌐 Coverage report
|
|
Lets add in some other common agent.yml fields as well, we have some covering add_*_metadata like container and cloud in most of our integrations, compare this with for example checkpoint. Rest LGTM! |
7e5065b to
1bf4967
Compare
Thanks for the review. I also realized that the host and message fields were missing in the remaining data streams and the events could contain those fields so I added them as well. |
|
/test |
1bf4967 to
601683c
Compare
|
Found a bug when processing the
so I have added the necessary processors in the ingest pipeline to meet the ECS format in case the field appears: 601683c |
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
601683c to
a6e019b
Compare
|
Package microsoft_sqlserver - 1.22.0 containing this change is available at https://epr.elastic.co/search?package=microsoft_sqlserver |
…6264) * Adjust mapping of host ECS fields in data streams * Update changelog * Add missing fields mapping to performance and transaction_logs datastreams * Convert host.mac to the expected format * Update version for Microsoft SQLServer

What does this PR do?
It adds the following changes:
Audit data stream
ecs.yml. Otherwise, they have been added atagent.ymlalong with missing fields forcloudandcontainer.host.os.nameis defined in ECS, it has been included inagent.ymlto avoid a conflict in the type of thetextmulti_field (textvsmatch_only_text) with the Log data stream.Log data stream
hostECS fields defined atagent.ymlhave been moved toecs.ymlfor consistency.Performance data stream
cloudandcontainerfields in agent.yml.hostfields in ecs.yml for consistency.Transaction logs data stream
cloudandcontainerfields in agent.yml.hostfields in ecs.yml for consistency.Checklist
changelog.ymlfile.Related issues
Screenshots