[AutoOps] Reference AutoOps solution on troubleshooting pages

[alaudazzi]

This PR updates the troubleshooting pages to reference AutoOps as the go-to solution.
Relates to https://github.com/elastic/obs-docs-projects/issues/279

[github-actions]

Documentation preview:

• ✨ Changed pages

[elasticsearchmachine]

@alaudazzi please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

[elasticsearchmachine]

Pinging @elastic/es-docs (Team:Docs)

[shainaraskas]

It will be automatically activated for your deployment, with no installation required.

these are elasticsearch docs, so this isn't true (AutoOps is cloud only).

this note is also very large and prominent. could we instead introduce autoops as an optional tool in the monitoring section instead of on all of the troubleshooting pages, with the caveat that it's available for cloud hosted only?

To avoid these docs needing an edit in future, it would be nice to not frame this as an announcement, and instead as one of the options we offer.

[alaudazzi]

Thank you for your feedback, @shainaraskas.
I'll let @arnonst the Opex PM chime in, as they requested this change in https://github.com/elastic/opex-product/issues/490.

[arnonst]

@alaudazzi @shainaraskas -
Regarding your above points:

1. AutoOps is now available for Cloud Hosted (in a few months for Self-managed as well).
2. As this is a new solutions, we want to give more context to the user about what is Autoops, whats the benefits and where to check if it is already supported in CSP regions used by their deployment. We can try to make is shorter, as we already gave it a few tries, we can look at it again.
3. Why having it on all pages, the reason is that user can go directly to a troubleshooting page and miss this announcment.

We want to make AutoOps the go-to solution for Elastic Cloud monitoring, it is free to use and available to all cloud users.

[shainaraskas]

@arnonst

AutoOps is now available for Cloud Hosted (in a few months for Self-managed as well).

these pages are shared by all of the deployment types, so we need to be very careful to provide that context, especially using language like "automatically activated". I'd prefer that we cut this down to something like "If you're using Elastic Cloud Hosted, then you can use AutoOps to xyz", perhaps with one "benefit" sentence, then link out.

Why having it on all pages, the reason is that user can go directly to a troubleshooting page and miss this announcment.

My main concern is the size and lifespan of these notes. Ideally, we'd explain how AutoOps would help them to identify this issue specifically to hint that AutoOps is relevant to them.

We want to make AutoOps the go-to solution for Elastic Cloud monitoring, it is free to use and available to all cloud users.

I agree that this is a good goal to have, but given the audience of these docs, we need to be more deliberate with our messaging.

[arnonst]

Thanks @shainaraskas for your comments.
Here is a shorter version which points out in a clear way that AutoOps is for ECH customers.

If you're using Elastic Cloud Hosted, then you can use AutoOps to significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths.
For more information, check Monitor with AutoOps, which is rolling out in phases across Elastic Cloud Hosted regions.

Can we go with this text?

[shainaraskas]

Consider the following edit. I recommend not including the rollout info here but instead in the "Monitor with AutoOps" topic so we only have to remove it in one place.

I'd also prefer this note to be below the overview for each page so people can understand what the page is about

If you're using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to Monitor with AutoOps.

[arnonst]

@shainaraskas I am OK with your suggestions.
I will work with @alaudazzi to adjust the text.

[alaudazzi]

@shainaraskas @arnonst
I integrated your suggestions, if you can have another look.

[leemthompo]

💚 All backports created successfully

Status	Branch	Result
✅	8.x
✅	8.17

Questions ?

Please refer to the Backport tool documentation