-
Notifications
You must be signed in to change notification settings - Fork 451
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
Migrate apache integration #370
Comments
Pinging @elastic/integrations-services (Team:Services) |
@andresrc I'm not sure if I understand these action items:
Pipeline tests use log files as test input. Once they're processed by ingest pipelines, the result is compared with generated output. I mean, pipeline tests require test log files and generated output, there is no way for them to exist without any of them. Did you think about sth else? EDIT: It looks like it was missed in the PR review: #342 (comment) |
As discussed offline with the team I will try to introduce a condition which will change the Metricbeat's behavior and emit adjusted fields under different names. |
Let's write down all action item in a convenient order:
(once Docker images for fleet are released, dashboards may stop working)
|
sorry, I'll remove the grok one, thanks! |
Changes partially merged, I will proceed with the next step:
|
It looks like there were issues in the unified release, which blocked releasing changes in Metricbeat. It will block:
|
All action items done. Resolving. |
Package / Dataset creation or update checklist
This checklist is intended for Devs which create or update a package to make sure they are consistent.
If the change targets a specific ES / Kibana / Agent version, uncomment this line and specify version.
Required Kibana version set to target version: 7.11.0We don't need to require Kibana 7.11.0 for this package.All Changes
Supported operating systems are documented (if applicable)At least a manual test with ES / Kibana / Agent has been performed.(covered by system tests)Dashboards
Log datasets
Metric datasets
This entry is currently recommended. It will be mandatory once we provide better support for it.
sample_event.json
) existsNew Packages
Screenshot of the Fleet "Add Integration" Page.The text was updated successfully, but these errors were encountered: