Skip to content

Remove EOL and deprecated Wavefront module #7625

Closed

Description

@shakuzen

Following up on #6328, it's time to consider removing the module. In general we would avoid doing that outside of a new major version, but given the EOL status of Wavefront, it is probably not disruptive to any users to remove this in a new minor that will release after a year of the Wavefront service being EOL.

Activity

  1. added this to the 1.18.0-M1 milestone on Jun 16, 2026
  2. added theissue type on Jun 16, 2026
  3. shakuzen commented on Jun 16, 2026

    @shakuzen
    MemberAuthor

    @jasonberanek on #6328 you asked for a heads up. We'd like to move forward with removing this module in the next minor version. Let us know if you have any concerns. We aren't planning with this to remove it from maintenance releases, so people who still need it for some reason (we'd like to understand what reason) can still use maintenance releases of 1.17.x and other lines while they are supported.

  4. shakuzen commented on Jun 16, 2026

    @shakuzen
    MemberAuthor

    If anyone else is still using the module for any reason, please let us know. Our working understanding is that no one should because the backend is dead, so switching to another Micrometer registry should be the migration path to something that isn't EOL.

  5. pinned this issue on Jun 16, 2026
  6. modified the milestones: 1.18.0-M1, 1.18.0-M2 on Aug 14, 2026
  7. Sharawey74 commented on Aug 28, 2026

    @Sharawey74

    I'd like to take this one if it's still open.

    I had a look at what's involved — the module directory itself, plus references in settings.gradle, docs/modules/ROOT/nav.adoc, the wavefront.adoc docs page, and three files under samples/micrometer-samples-core.

    Two questions before I start:

    1. Would you accept a PR for this from outside the team, or would you rather handle it yourselves as part of release prep?
    2. Which branch should it target? You mentioned the next minor version, so I want to make sure I don't put it on the wrong one.
  8. added
    release notesNoteworthy change to call out in the release notes
    and removed on Sep 17, 2026
  9. changed the issue type fromtoon Sep 17, 2026
  10. self-assigned this
    on Sep 17, 2026
  11. shakuzen commented on Sep 17, 2026

    @shakuzen
    MemberAuthor

    @Sharawey74 thank you for the offer to help with this. We were waiting for feedback from users to help decide whether we would remove this module in the 1.18.0-M2 milestone or not. Since we are running out of time to make changes in the M2 release, it will be easier for us to take care of this ourselves.

  12. added a commit that references this issue on Sep 17, 2026
    63127cf
  13. jonatan-ivanov commented on Sep 17, 2026

    @jonatan-ivanov
    Member

    @jasonberanek on #6328 you asked for a heads up. The Wavefront registry is going to be removed in 1.18.0 (release targeted towards the end of 2026). Nothing is going to change in 1.17.x and earlier versions, you can continue using them (ideally as long as they are supported: https://micrometer.io/support/).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

registry: wavefrontA Wavefront (Tanzu Observability) Registry related issuerelease notesNoteworthy change to call out in the release notes

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions