Update Observability AI Assistant docs

[mdbirnstiehl]

This PR closes Issue 3139

I've added the new set up instructions using the connector, added details about chat and functions, and updated the requirements.

Preview here.

A couple of questions:

• Do we need to add requirements for knowledge base?
• I updated the requirements to specifically mention gpt-4, but do we want to clarify more that they technically can use 3.5, but the experience will be worse?

[github-actions]

A documentation preview will be available soon:

• 📚 HTML diff
• 📙 Observability Guide

[dgieselaar]

@mdbirnstiehl:

Do we need to add requirements for knowledge base?

Yes! Especially the part about it requiring a 4gb ML node. I think this is part of the trial now, but good to clarify anyway.

I updated the requirements to specifically mention gpt-4, but do we want to clarify more that they technically can use 3.5, but the experience will be worse?

Sgtm. @SeanHeelan can you also chime in?

[almudenasanz]

@mdbirnstiehl we have updated the contextual prompt for alerting - logs and now it supports spikes or drops, so we renamed it to "log rate change", so we would need to update this line in the docs:

Alerting — provides possible log spike causes and remediation suggestions.

[CoenWarmer]

@mdbirnstiehl Could you also include instructions on how to add information to the Assistant's knowledge base by indexing documents? @almudenasanz wrote up the steps over here.

Just to be clear, there's two ways of adding information to the knowledge base at the moment:

• A user can ask the Assistant to remember something. Doing that will cause the Assistant to use the summarize function and store the resulting information into the knowledge base. Example: "My name is John. Remember that."
• A user can manually add information directly into the index via Elasticsearch APIs (described above in Almu's write up).

In 8.11 we want to offer a way to do this via GUI as well.

[mdbirnstiehl]

@almudenasanz @CoenWarmer @dgieselaar I've made the suggested updates if you wouldn't mind taking another look. Thank you!

[dgieselaar]

Looks good, would like @SeanHeelan to take a look

[SeanHeelan]

Looks good to me, bar the one issue I've pointed out

[bmorelli25]

Looks good. Just a few nitpicks.