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

[main](backport #4143) O11y AI Assistant - Google Gemini support #4407

Merged
merged 3 commits into from
Oct 19, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 18, 2024

We document Google Gemini in the connectors https://www.elastic.co/guide/en/kibana/current/gemini-action-type.html and in our release highlights https://www.elastic.co/guide/en/observability/current/whats-new.html, but it's missing from the o11y docs.

Add this mention to any place we list the supported connectors with the O11y AI Assistant.

TODO after merging:

* AI Assistant Gemini AI

* Add google gemini details

* Specify supported models of Gemini

* Apply changes from review

---------

Co-authored-by: dedemorton <[email protected]>
(cherry picked from commit 4143855)

# Conflicts:
#	docs/en/observability/observability-ai-assistant.asciidoc
@mergify mergify bot requested a review from a team as a code owner October 18, 2024 21:54
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Oct 18, 2024
Copy link
Contributor Author

mergify bot commented Oct 18, 2024

Cherry-pick of 4143855 has failed:

On branch mergify/bp/main/pr-4143
Your branch is up to date with 'origin/main'.

You are currently cherry-picking commit 41438555.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/en/observability/observability-ai-assistant.asciidoc

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Copy link
Contributor

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@bmorelli25 bmorelli25 enabled auto-merge (squash) October 18, 2024 23:43
@bmorelli25 bmorelli25 removed conflicts There is a conflict in the backported pull request needs-writer-review labels Oct 18, 2024
Copy link
Contributor

@dedemorton dedemorton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (assuming CI passes)

@bmorelli25 bmorelli25 merged commit ca46453 into main Oct 19, 2024
3 checks passed
@bmorelli25 bmorelli25 deleted the mergify/bp/main/pr-4143 branch October 19, 2024 00:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants