-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Remove support for deprecated xpack.telemetry configurations #51142
Conversation
Pinging @elastic/kibana-docs (Team:Docs) |
Pinging @elastic/kibana-stack-services (Team:Stack Services) |
💚 Build Succeeded
|
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.
We need to remove a few extra lines of code from the telemetry plugin and xpack_main before merging this on master.
@Bamieh Can you clarify? I'm not aware of the code you're referring to, but I'll go remove it if you point me in its direction. |
@gchaps Can you help me out on this docs failure? I'm not sure how since this is simply adding a new section that doesn't link outward, but apparently it broke the stack upgrade docs? |
docs/migration/migrate_8_0.asciidoc
Outdated
The `xpack.` prefix has been removed for all telemetry configurations. | ||
|
||
*Impact:* | ||
For any configurations beginning with `xpack.telemetry.`, remove the `xpack.` prefix. For example, use <<telemetry.enabled, `telemetry.enabled`>> instead. |
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.
Because this content gets pulled into the Stack docs, the link needs to be formatted as follows:
{kibana-ref}/monitoring-settings-kb.html#monitoring-general-settings[telemetry.enabled]
Note: This link goes to the section heading because I was unable to get the link to telemetry.enabled to work. Also, linking to the section heading gives the reader more context.
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.
@afharo i believe we need to address this one before merging.
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.
yup! It's even failing the build. I'll work on it today...
I was wondering why we have that config parameter in the monitoring file instead of a specific doc file for telemetry where we can explain all the configuration properties.
@epixa I believe your comment is before our sync today where we've discussed these changes. If you still need me to write them in a comment please let me know. |
Pinging @elastic/pulse (Team:Pulse) |
@Bamieh Would you mind taking ownership of this task please? It's not urgent. |
In 7.5, we moved telemetry to OSS and dropped the xpack prefix for the telemetry plugin configuration options. We deprecated the usage of the xpack prefix so any existing usage would trigger a warning at startup. In 8.0, we remove support for the deprecated xpack prefix configs for telemetry.
3e908f4
to
4996348
Compare
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 for platform changes
Co-Authored-By: gchaps <[email protected]>
Co-Authored-By: gchaps <[email protected]>
Co-Authored-By: gchaps <[email protected]>
Co-Authored-By: gchaps <[email protected]>
Co-Authored-By: gchaps <[email protected]>
Co-Authored-By: gchaps <[email protected]>
Co-Authored-By: gchaps <[email protected]>
Co-Authored-By: gchaps <[email protected]>
Co-Authored-By: gchaps <[email protected]>
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
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.
@afharo we need to remove the telemetry configs from xpack_main
:
x-pack/legacy/plugins/xpack_main/index.js
@Bamieh good call! I'm surprised it was there anyway... since that file enforces Anyway... removed! |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
@afharo it was needed to support the legacy config to be passed to the kibana configs. |
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
* master: Switch to embeddable factory interface with optional override (elastic#61165) fix text error in diagrams (elastic#62101) [Index management] Prepare support Index template V2 format (elastic#61588) Updates dashboard images (elastic#62011) [Maps] remove MapBounds type (elastic#62332) [Uptime] Convert anomaly Jobs name to lowercase to comply with… (elastic#62293) Make d3 place nicely with object values (elastic#62004) EMT-287: update schema with elastic agent id (elastic#62252) [Maps] fix replaceLayerList to handle case where map is not intialized (elastic#62202) Remove support for deprecated xpack.telemetry configurations (elastic#51142) [Uptime] Remove static constant for index name completely (elastic#62256) [APM] E2E: install dependencies for vanilla workspaces (elastic#62178) [backport] Bump to 5.1.3 (elastic#62286) Show server name in Remote Cluster detail panel (elastic#62250) Rename some alert types (elastic#61693) changing duration type to ms, s, m (elastic#62265) [ML] Clear Kibana index pattern cache on creation or form reset. (elastic#62184) Move `src/legacy/server/index_patterns` to data plugin (server) (Remove step) (elastic#61618) [NP] Remove IndexedArray usage in Schemas (elastic#61410)
Friendly reminder: Looks like this PR hasn’t been backported yet. |
This is for |
Pinging @elastic/kibana-core (Team:Core) |
In 7.5, we moved telemetry to OSS and dropped the xpack prefix for the
telemetry plugin configuration options. We deprecated the usage of the
xpack prefix so any existing usage would trigger a warning at startup.
In 8.0, we remove support for the deprecated xpack prefix configs for
telemetry.
Closes #51141