Skip to main content

3 posts tagged with "dashboards"

View All Tags

Launch a Search Workspace: Managed OpenSearch Plus Dashboards in Minutes

· 4 min read
FoundryDB Team
Engineering @ FoundryDB

Standing up a search stack usually starts the same way every time. Provision an OpenSearch cluster. Stand up Dashboards next to it. Wire Dashboards to the cluster with an endpoint and credentials you paste into a config file. Make sure the security plugin lets the two talk. Decide where Dashboards keeps its saved objects. Only then do you get to the part you actually wanted: indexing data and running a query.

The Launch a search workspace stack collapses that into one button. You get a managed OpenSearch cluster and a full OpenSearch Dashboards workspace, attached and EU-resident, in minutes, with nothing to wire by hand.

search-workspace stack composition & launch
RUNNING Stack wired · search workspace live
Stack Templatesearch-workspacelaunch ⇉OpenSearchcluster · :9200OpenSearch Dashboardsattach + saved objects → clusterserve →Search WorkspaceDiscover · dashboards · Dev Tools
Template · launchOpenSearch (cluster)OpenSearch Dashboards (console)wiring (attach + saved objects)

Launch a BI workspace: Metabase on your own PostgreSQL, in minutes

· 4 min read
FoundryDB Team
Engineering @ FoundryDB

Getting to your first dashboard is rarely about the dashboard. It is about provisioning a database, standing up a BI tool, opening a port, copying a connection string, and praying the two halves agree on TLS. By the time anything renders, the afternoon is gone and the chart you actually wanted is still a row in a spreadsheet.

The Launch a BI workspace stack collapses all of that into one launch. You get a complete Metabase workspace wired to your own PostgreSQL, EU-resident, with dashboards in minutes. You do not assemble it. You launch it.

BI workspace stack composition
RUNNING Stack wired · BI workspace live
Stack Templatebi-workspacelaunch ⇉PostgreSQLtier-2Metabaseattaches dbserve →BI Workspacedashboards
TemplatePostgreSQLMetabase · BI workspacewiring (connection injected)

Full-Text Search with Managed OpenSearch: From Zero to Production

· 7 min read
FoundryDB Team
Engineering @ FoundryDB

Every application eventually outgrows LIKE '%query%'. Once your product catalog, help center, or log pipeline crosses a few million documents, you need an inverted index, not a sequential scan. OpenSearch provides exactly that: full-text search with relevance scoring, custom analyzers, aggregations, and a visualization layer built in.

The hard part is running it. JVM heap tuning, cluster formation, TLS certificate management, shard rebalancing, and snapshot configuration turn a "quick search feature" into a permanent ops project. FoundryDB removes all of that. You get a managed OpenSearch 2.19 cluster with TLS, authentication, automated snapshots, and monitoring out of the box.

This guide walks through deploying OpenSearch on FoundryDB and building production-quality search: from provisioning to index design, full-text queries, custom analyzers, and aggregations.

OpenSearch cluster, query fan-out & gather
Cluster green · search fans out to one copy per shard, then gathers
Coordinatorfan-out / gatherquery →Data nodesP0 P1 P2 · R0 R1 R2⇠ hitsCluster-managershard allocation
Cluster-managerCoordinatorData nodePrimary shardReplica shardcluster state / gather (dashed)