-
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
[O11y] Migrate infraobs packages to ecs@mappings #10171
[O11y] Migrate infraobs packages to ecs@mappings #10171
Conversation
s/10135/10171/ in PR description. Also suggest using sha 014b35dfe4c9832b51e7c909a39a48257d6a005d for the tool; f7c19f8f3fa105fe1d869ed34f4d6c76c75bce2c is out of date with some fixes. To fix up issues the best thing to do is reset --hard origin/main and re-run the command with the correct values, rather than polishing the PR. |
Cool, let me do that. Thanks! |
🚀 Benchmarks reportTo see the full report comment with |
The issues with the sample events will need addressing. The approach that I have taken is to do manual fix-ups guided by the failures that I see after running the tool (for example here) and then run the tool after those fixes are merged. |
c98e090
to
53365dc
Compare
…anual_ecs_mapping_migration Conflicts: packages/cassandra/changelog.yml
…anual_ecs_mapping_migration Conflicts: packages/rabbitmq/changelog.yml
ignore_empty_value: true | ||
ignore_failure: true | ||
- append: | ||
field: event.category | ||
value: | ||
- log | ||
value: ["network"] |
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.
@harnish-elastic Can you please explain this change?
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 change was related to event.category will not be longer support the value log
. So based on data stream's logs, the network
value suits. Hence updated the value!
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.
Can you share what the exact error here and since when has this category been removed ?
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.
oracle_weblogic/access test-access.log:
[0] parsing field value failed: field "event.category"'s value "log" is not one of the allowed values (api, authentication, configuration, database, driver, email, file, host, iam, intrusion_detection, library, malware, network, package, process, registry, session, threat, vulnerability, web)
ignore_empty_value: true | ||
ignore_failure: true | ||
- append: | ||
field: event.category | ||
value: | ||
- log | ||
value: ["network"] |
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.
Can you share what the exact error here and since when has this category been removed ?
…anual_ecs_mapping_migration Conflicts: packages/prometheus/changelog.yml packages/prometheus/docs/README.md packages/prometheus/manifest.yml
💚 Build Succeeded
History
|
Quality Gate failedFailed conditions |
ignore_empty_value: true | ||
ignore_failure: true | ||
- append: | ||
field: event.category | ||
value: | ||
- log | ||
value: ["iam"] |
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.
When i look at the attached screenshot of this PR, i do not think that we must limit the event.category to iam
only.
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.
To unblock this PR, lets keep in "iam" for now.
If we come to a consensus that we need to add more categories, we can do that later as we are appending here.
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.
prometheus.remote_write - 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.
Looks good!
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
Package cassandra - 1.14.0 containing this change is available at https://epr.elastic.co/search?package=cassandra |
Package nats - 1.7.0 containing this change is available at https://epr.elastic.co/search?package=nats |
Package oracle_weblogic - 1.7.0 containing this change is available at https://epr.elastic.co/search?package=oracle_weblogic |
Package prometheus - 1.18.0 containing this change is available at https://epr.elastic.co/search?package=prometheus |
Package rabbitmq - 1.15.0 containing this change is available at https://epr.elastic.co/search?package=rabbitmq |
Package spring_boot - 1.6.0 containing this change is available at https://epr.elastic.co/search?package=spring_boot |
Package sql - 0.5.0 containing this change is available at https://epr.elastic.co/search?package=sql |
Package stan - 1.7.0 containing this change is available at https://epr.elastic.co/search?package=stan |
Package statsd_input - 0.4.0 containing this change is available at https://epr.elastic.co/search?package=statsd_input |
Proposed commit message
Migration performed using ecs-update. Minor manual changes are performed.
event.category or event.type is expecting value as an array instead of string. Hence provided the value as an array.
generated pipeline and system tests.
If the package is containing kibana version configuration as below,
Updated these configuration to,
Command
Checklist
changelog.yml
file.TSDB Testing