You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we documented the Gemini connector in the Observability AI Assistante docs (#4143), we agreed to point users to the connector documentation as the source of truth for what is supported/required.
@lucabelluccini made the following comment indicating that we need to converge on which recommendations to make in the connector docs vs the Observability docs. This feedback requires further discussion before implementing, so I'm opening this follow-up issue. Here is the text of Luca's comment:
"As the AI Connector of Platform can be used by both O11y & Security, we should try to converge what's common in the connectors docs and recommendations for O11y in the O11y AI docs, notably:
we do not recommend BYO-LLM (Security seems to "allow" it)
you need a non-free tier or otherwise you'll hit rate limiting immediately - this might be applicable to all connectors(?)
function calling and switch to simulate function calling - this might be applicable to all connectors(?)
O11y might be tested only with specific 3rd party vendors and models and maybe in the future the platform offering will diverge vs O11y or Security specific recommendations"
This work will require coordination with the team that documents connectors and the security writers.
Description
When we documented the Gemini connector in the Observability AI Assistante docs (#4143), we agreed to point users to the connector documentation as the source of truth for what is supported/required.
@lucabelluccini made the following comment indicating that we need to converge on which recommendations to make in the connector docs vs the Observability docs. This feedback requires further discussion before implementing, so I'm opening this follow-up issue. Here is the text of Luca's comment:
"As the AI Connector of Platform can be used by both O11y & Security, we should try to converge what's common in the connectors docs and recommendations for O11y in the O11y AI docs, notably:
This work will require coordination with the team that documents connectors and the security writers.
Resources
n/a
Which documentation set does this change impact?
Stateful and Serverless
Feature differences
No difference AFAIK.
What release is this request related to?
N/A
Collaboration model
The documentation team
Point of contact.
Main contact: @emma-raffenne
Stakeholders:
The text was updated successfully, but these errors were encountered: