Publish 8.0+ compatible versions of stack monitoring integrations

[jasonrhodes]

[WIP]

The experimental stack monitoring integrations that were published to the package registry in 7.x were not versioned so that they would be compatible with 8.x versions of the Elastic stack. Because of this, anyone who has any of these integrations installed will have issues upgrading to 8.x versions of the stack, unless they first uninstall these integrations (or upgrade them to a compatible version).

I've already made the changes for the Logstash

• Logstash
• Elasticsearch
• Kibana
• APM
• Others?

[elasticmachine]

Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI)

[jasonrhodes]

@joshdover can you help me with two questions re: this work?

(1) You mentioned a fix went out in 8.0.1 for the Fleet side of this problem, can you link to that PR?

(2) Do you know if it's possible for us to unpublish some of these packages that were experimental/prerelease? @ravikesarwani would prefer to remove them since they haven't been tested even for experimental release (they were accidentally published as GA at one point in 7.x and we fixed that by downgrading them to experimental). I was under the impression this might be impossible or extremely messy so I left them as experimental while we wait to test them, but it's looking like that process may take a bit longer and we'd prefer to remove them if that's possible.

Thanks!

[joshdover]

(1) You mentioned a fix went out in 8.0.1 for the Fleet side of this problem, can you link to that PR?

#125525 - note this only fixes the problem where Fleet doesn't boot at all, there's still other broken experiences for users who had installed these packages, but they're much less impactful.

Namely, if they try to open the integration from the Installed Integrations page, they'll get something like this:

IMO this is probably fine and we can document a workaround to delete any package policies using this integration and uninstall the package.

(2) Do you know if it's possible for us to unpublish some of these packages that were experimental/prerelease?

I'm not sure the process for this, but I think it's generally frowned upon. @mtojek could answer more thoroughly than I.

[mtojek]

(2) Do you know if it's possible for us to unpublish some of these packages that were experimental/prerelease?

Technically it's possible, but this is highly discouraged as you may break the setup for people who have already installed those. We agree to remove packages if they are so broken that nobody can even install them. Currently, the process requires manually removing packages from the Package Storage repository.

[jasonrhodes]

@ravikesarwani FYI, I think this likely confirms it's too risky to unpublish the monitoring packages, to close this loop. I suggest we move forward with the experimental packages and clear documentation as much as possible.

[ravikesarwani]

okay, thanks for following up on this and giving it a try.