Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AI Assistant]: Document recommendations for using the Gemini connector #4410

Open
dedemorton opened this issue Oct 18, 2024 · 0 comments
Open

Comments

@dedemorton
Copy link
Contributor

dedemorton commented Oct 18, 2024

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:

  • 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.

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:

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

No branches or pull requests

1 participant