OpenSearch
Run read-only SQL queries against your OpenSearch cluster and bring the results into the sheet.
The OpenSearch connector runs a SQL query of your choice, read-only, against an OpenSearch cluster you manage: no OAuth required, it uses the host, port, username and password you enter when connecting. It uses OpenSearch's built-in SQL plugin (not a JDBC driver, and not OpenSearch's native JSON query language), so you write a normal SQL query and specify the index directly in the FROM clause (e.g. SELECT * FROM my_index) - there is no separate "database" to select when connecting.
Only SELECT queries are allowed (optionally preceded by WITH): no DELETE or other write operations, checked before every run.
Array fields: if a field in your index holds multiple values (an array), the connector joins them into a single comma-separated text value when writing the report, since a spreadsheet cell cannot hold a native list.
Tip for daily updates: to automatically pull only new data every day (e.g. with a schedule and "Append new results to old" enabled), no special mechanism is needed: write a condition directly in the query using a date field, evaluated at execution time, e.g. WHERE event_datetime >= NOW() - INTERVAL 1 DAY. The saved query text never changes, but the result changes every day because the condition is evaluated when the report runs, not when you write the query once.
Available metrics
There are no fixed metrics or dimensions: the report columns are exactly the columns your SQL query returns (the column names or aliases used in the SELECT).
Known limits
- SELECT-only queries (or WITH)One statement per query, no DELETE or other write operations: checked before every run. Note that OpenSearch's SQL plugin natively supports DELETE as well as SELECT, so this check is the only real safeguard, not just an extra precaution. A query that fails this check shows an error instead of running.
- No test when you connectThe connection page saves what you enter without testing it: the real test happens the first time you select that connection to configure a report, not when you create it.
- The server must be reachable from the internetDoes not work with local networks or behind a VPN. Uses OpenSearch's SQL plugin over HTTP (not JDBC), which must be enabled on the cluster (enabled by default): the server firewall must allow the IP ranges Google publishes at gstatic.com/ipranges/goog.json, and the port must be 1025 or higher (standard 9200 is fine).
- HTTP by default, with an HTTPS optionBy default the connection uses plain HTTP (port 9200). If your OpenSearch server requires an encrypted connection — common on managed services, which usually require it — check "Use HTTPS" when connecting. Always use a dedicated user with read-only permissions, regardless of this setting.