Gemini connector integration

[honeyn303]

Gemini Connector: Supports Google Gemini AI API

New Generative AI for Security connector. Allows user to define a Google Gemini AI connector.

Currently has the most basic executor RUN/TEST action to send request to the chat completion endpoint and receive back the response. Also implements the DASHBOARD to create the token tracking dashboard.

Example Gemini payload:

{
  "contents":[
    {
      "role":"user",
      "parts":[
        {
          "text":"Write the first line of a story about a magic backpack."
        }
      ]
    }
  ],
  "generation_config":{
    "temperature":0,
    "maxOutputTokens":8192
  }
}

Define connector

Test connector

Token Dashboard

Testing

Credentials for Google Gemini: https://p.elstc.co/paste/8sS2cMve#lWhE4ppTH9kVy2zm04egNxtrqO3AbU1C31GvMtvqYVF

1. Create Gemini connectors with provided credentials
2. Use elastic-product as the project
3. Use the entire JSON payload in the PasteBin link as the Credentials JSON
4. Test the connector by sending example payload
5. Confirm results in Network tab. Should look like:

6. Once you've successfully sent a message, navigate back to the connector edit tab and click the link to the token tracking dashboard
7. Ensure the dashboard reflects the data you sent in the test

[stephmilovic]

buildkite test this

No longer changes search_playground code

[stephmilovic]

buildkite test this

[peluja1012]

/ci

[ersin-erdal]

LGTM, everything looks in line with the best practices.

Just not sure about removing .yarnrc, even if it is a must, should it be in this PR?

[sphilipse]

Deleting .yarnrc and adding a 147 kilobyte .yarn/releases/yarn-1.22.19.cjs file is definitely wrong, please revert those changes.

If yarn setup changes are needed, this PR is not the right place to do them and that'll require more discussion in a wider forum than just pushing it here.

[honeyn303]

Deleting .yarnrc and adding a 147 kilobyte .yarn/releases/yarn-1.22.19.cjs file is definitely wrong, please revert those changes.

If yarn setup changes are needed, this PR is not the right place to do them and that'll require more discussion in a wider forum than just pushing it here.

@sphilipse I have reverted these changes.

[stephmilovic]

buildkite test this

[sphilipse]

There are still significant changes to .yarnrc that shouldn't be there. We should not need to mess with .yarnrc

[honeyn303]

There are still significant changes to .yarnrc that shouldn't be there. We should not need to mess with .yarnrc

@sphilipse sure, this is done now

[stephmilovic]

@elasticmachine merge upstream

[stephmilovic]

buildkite test this

[stephmilovic]

buildkite test this

[stephmilovic]

buildkite test this

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 00298b4
• Cloud Deployment

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
stackConnectors	249	258	+9

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
stackConnectors	533.4KB	560.7KB	+27.3KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
kbnUiSharedDeps-npmDll	6.3MB	6.3MB	+9.6KB
stackConnectors	51.1KB	52.6KB	+1.5KB
total			+11.1KB

Unknown metric groups

async chunk count

id	before	after	diff
stackConnectors	82	87	+5

ESLint disabled line counts

id	before	after	diff
stackConnectors	107	113	+6

Total ESLint disabled count

id	before	after	diff
stackConnectors	113	119	+6

History

• 💚 Build #214315 succeeded 61666f3
• 💔 Build #214174 failed e7a07db
• 💔 Build #214151 failed f967c76
• 💔 Build #213738 failed c738d03
• 💔 Build #213690 failed 0dfce94

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream