Elastic Agent: ensure syslog processor is not used with 7.17.X agents#10471
Elastic Agent: ensure syslog processor is not used with 7.17.X agents#10471pierrehilbert merged 2 commits intomainfrom
Conversation
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
|
|
@norrietaylor @lalit-satapathy @andrewkroh can we please get people from your time to review this? |
andrewkroh
left a comment
There was a problem hiding this comment.
Do we expect all packages to work on Elastic Agent 7.17 even when their manifest says they require Kibana 8.x? Or is this a special case because it's the system package?
Are there CI tests for this package against 7.x?
As we never introduced any Agent version constraints in the package manifest then users would expect them to work. If you first upgrade your stack to 8.X and then upgrade all integrations before upgrading Agents you wouldn't expect them to be broken.
I do not think so. |
|
@pierrehilbert @cmacknz |
|
@ishleenk17 That what would you recommend? It also means that 7.X users won't get fixes anymore or this will break their integrations? |
|
Approving this for now as it's a conditional check.
In general, the recommendation would be to not have a mix of versions in the stack. There can be other uncovered incompatibilities as well. For fixing an integration in older stack version, this approach can be followed. |
I do agree but this is definitely not what users are doing and this can be easily proved by our telemetry. |
|
Package system - 1.59.1 containing this change is available at https://epr.elastic.co/search?package=system |




Proposed commit message
Elastic Agent: ensure syslog processor is not used with 7.17.X agents by adding a condition.
Checklist
changelog.ymlfile.Author's Checklist
Tests:
configuringif I reverse the condition checkHow to test this PR locally
Related issues
Screenshots