-
Notifications
You must be signed in to change notification settings - Fork 474
Jlind23/deprecate loginput #12503
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
Jlind23/deprecate loginput #12503
Conversation
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
security |
2898.55 | 1715.27 | -1183.28 (-40.82%) | 💔 |
To see the full report comment with /test benchmark fullreport
@elastic/sec-linux-platform could you help me understand why the auditd package tests are failing? |
@@ -1,6 +1,6 @@ | |||
name: iis | |||
title: IIS | |||
version: "1.21.1-next" | |||
version: "1.22.0" |
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.
Do we know why it had the -next
prefix before? Is it okay to drop it?
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.
That means this was a pre-release not shipped to end users. I would need @lalit-satapathy's inputs 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.
If it was a pre-release I assume we would have to keep it.
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.
-next
, apart from being a prerelease suffix, it avoids publishing the package. So if you add a version without this suffix it will also publish previously unreleased changes.
Though I am not sure why the previous change was included under a -next
suffix, it only adds definitions for new fields, it looks safe and releaseable.
@stefans-elastic @muthu-mps do you see any reason not to release #12070?
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.
@jsoriano,
The -next
tag was added to have the newer fields available from 8.17.x version and user has to upgrade the stack to get monitor those fields. I have noticed there was a similar discussion around handing such a scenario without upgrading the Kibana version. We can drop the pre-release tag.
@@ -1,6 +1,6 @@ | |||
name: iis | |||
title: IIS | |||
version: "1.21.1-next" | |||
version: "1.22.0" |
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.
-next
, apart from being a prerelease suffix, it avoids publishing the package. So if you add a version without this suffix it will also publish previously unreleased changes.
Though I am not sure why the previous change was included under a -next
suffix, it only adds definitions for new fields, it looks safe and releaseable.
@stefans-elastic @muthu-mps do you see any reason not to release #12070?
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. This is a no-op until we make the change in Beats to refuse to start the log input without the allow_depreacted_use: true
flag when it is run from Elastic Agent. Right now there is an exception for this. We would want this change made first regardless so that integrations aren't temporarily broken we do that.
@elastic/obs-ds-hosted-services @elastic/obs-infraobs-integrations @elastic/sec-deployment-and-devices @elastic/sec-linux-platform @elastic/sec-windows-platform @elastic/security-service-integrations @elastic/stack-monitoring |
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.
LGT Stack Monitoring
Package ibmmq - 1.5.0 containing this change is available at https://epr.elastic.co/package/ibmmq/1.5.0/ |
Package iis - 1.22.0 containing this change is available at https://epr.elastic.co/package/iis/1.22.0/ |
Package infoblox_nios - 1.27.0 containing this change is available at https://epr.elastic.co/package/infoblox_nios/1.27.0/ |
Package iptables - 1.19.0 containing this change is available at https://epr.elastic.co/package/iptables/1.19.0/ |
Package kafka - 1.17.0 containing this change is available at https://epr.elastic.co/package/kafka/1.17.0/ |
Package kibana - 2.6.0 containing this change is available at https://epr.elastic.co/package/kibana/2.6.0/ |
Package logstash - 2.5.0 containing this change is available at https://epr.elastic.co/package/logstash/2.5.0/ |
Package microsoft_defender_endpoint - 2.28.0 containing this change is available at https://epr.elastic.co/package/microsoft_defender_endpoint/2.28.0/ |
Package microsoft_exchange_online_message_trace - 1.26.0 containing this change is available at https://epr.elastic.co/package/microsoft_exchange_online_message_trace/1.26.0/ |
Package microsoft_sqlserver - 2.11.0 containing this change is available at https://epr.elastic.co/package/microsoft_sqlserver/2.11.0/ |
Package mongodb - 1.18.0 containing this change is available at https://epr.elastic.co/package/mongodb/1.18.0/ |
Package nats - 1.8.0 containing this change is available at https://epr.elastic.co/package/nats/1.8.0/ |
Package osquery - 1.21.0 containing this change is available at https://epr.elastic.co/package/osquery/1.21.0/ |
Package platform_observability - 0.1.0 containing this change is available at https://epr.elastic.co/package/platform_observability/0.1.0/ |
Package postgresql - 1.26.0 containing this change is available at https://epr.elastic.co/package/postgresql/1.26.0/ |
Package pps - 0.4.0 containing this change is available at https://epr.elastic.co/package/pps/0.4.0/ |
Package rabbitmq - 1.17.0 containing this change is available at https://epr.elastic.co/package/rabbitmq/1.17.0/ |
Package santa - 3.23.0 containing this change is available at https://epr.elastic.co/package/santa/3.23.0/ |
Package snort - 1.17.0 containing this change is available at https://epr.elastic.co/package/snort/1.17.0/ |
Package sophos - 3.12.0 containing this change is available at https://epr.elastic.co/package/sophos/3.12.0/ |
Package stan - 1.8.0 containing this change is available at https://epr.elastic.co/package/stan/1.8.0/ |
Package suricata - 2.23.0 containing this change is available at https://epr.elastic.co/package/suricata/2.23.0/ |
Package system - 1.66.0 containing this change is available at https://epr.elastic.co/package/system/1.66.0/ |
Package thycotic_ss - 1.11.0 containing this change is available at https://epr.elastic.co/package/thycotic_ss/1.11.0/ |
Package traefik - 2.4.0 containing this change is available at https://epr.elastic.co/package/traefik/2.4.0/ |
Package zeek - 2.27.0 containing this change is available at https://epr.elastic.co/package/zeek/2.27.0/ |
@@ -11,7 +11,7 @@ categories: | |||
- observability | |||
conditions: | |||
kibana: | |||
version: "^8.13.0 || ^9.0.0" | |||
version: "^8.13.0" |
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 guess this change was unintended, reverting it in #13315.
With the introduction of elastic/beats#42295 the log input will soon not be able to run anymore as it is deprecated. To continue running we need to add this allow deprecated parameter to all log input template.