<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/dasha-1-8-index-recommendations-i-o-analysis-schema-checks-and-log-insights-ugyubqr7o" -->

---
title: Dasha 1.8: index recommendations, I/O analysis, schema...
description: Dasha 1.8, an open source read-only performance dashboard for PostgreSQL fleets, adds several major features: automatic index recommendations built from...
canonical: https://daily.dev/posts/dasha-1-8-index-recommendations-i-o-analysis-schema-checks-and-log-insights-ugyubqr7o
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Dasha 1.8: index recommendations, I/O analysis, schema checks and log insights | daily.dev
og:description: Dasha 1.8, an open source read-only performance dashboard for PostgreSQL fleets, adds several major features: automatic index recommendations built from...
og:url: https://daily.dev/posts/dasha-1-8-index-recommendations-i-o-analysis-schema-checks-and-log-insights-ugyubqr7o
og:image: https://api.daily.dev/og/posts/UGyuBqr7O.png
og:image:alt: Dasha 1.8: index recommendations, I/O analysis, schema checks and log insights
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Dasha 1.8: index recommendations, I/O analysis, schema checks and log insights

**[PostgreSQL](https://daily.dev/sources/postgres)** · 5 min read · 0 upvotes · 0 comments

## Summary

Dasha 1.8, an open source read-only performance dashboard for PostgreSQL fleets, adds several major features: automatic index recommendations built from pg_stat_statements and auto_explain data, an I/O analysis page based on pg_stat_io (PostgreSQL 16+), 17 schema checks for structural defects (including a CVE-2018-1058 check), and log insights integrating with OpenSearch, Elasticsearch, VictoriaLogs and Yandex Managed PostgreSQL. Other additions include per-database query analysis, Postgres Pro support via pgpro_stats, automatic database discovery, a Health Score composite metric, automatic snapshot capture on activity spikes, deeper index bloat/duplicate analysis, and a read-only MCP connector exposing 31 diagnostic tools to AI assistants. Requires PostgreSQL 14+ for monitored clusters (I/O page needs 16+), with a role holding pg_monitor and CONNECT privileges.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.postgresql.org/about/news/dasha-18-index-recommendations-io-analysis-schema-checks-and-log-insights-3387>

## Questions this post answers

### What new features does Dasha 1.8 add for PostgreSQL monitoring?

Dasha 1.8 adds automatic index recommendations derived from pg_stat_statements and auto_explain plans, an I/O analysis page built on pg_stat_io for PostgreSQL 16 and newer, 17 schema checks for structural defects such as sequences near exhaustion and tables without primary keys, and log insights integrating with OpenSearch, Elasticsearch, VictoriaLogs and Yandex Managed PostgreSQL. It also adds a read-only MCP connector with 31 diagnostic tools for AI assistants.

_Teams tracking new PostgreSQL tooling releases can follow updates like this one on daily.dev._

### What PostgreSQL version is required to use the I/O analysis page in Dasha?

The I/O page requires PostgreSQL 16 or newer because it is built on the pg_stat_io view, which was introduced in that version. Server I/O is broken down by backend type, object and context (normal, vacuum, bulkread, bulkwrite), with WAL breakdown available on PostgreSQL 18. Dasha itself supports monitoring clusters running PostgreSQL 14 through 18.

_Engineers planning a PostgreSQL upgrade can track version-specific feature gaps like this on daily.dev._

### What permissions does a monitoring tool need to connect to a PostgreSQL cluster without installing an agent?

A read-only role with the pg_monitor privilege and CONNECT access on every monitored database is sufficient for agentless PostgreSQL monitoring. This approach, used by Dasha, requires no agent or extension installed on the database hosts beyond ones already present, such as pg_stat_statements for query statistics and optionally pgstattuple for bloat analysis.

_Developers weighing agentless database monitoring setups can compare options on daily.dev._

## Similar posts on daily.dev

- [Dasha - performance dashboard](https://daily.dev/posts/dasha---performance-dashboard-cm6mu78wl) · PostgreSQL · 1 upvotes · 0 comments
- [Discover Databases, starting with Postgres](https://daily.dev/posts/discover-databases-starting-with-postgres-vudl6ia8e) · Last9 · 1 upvotes · 0 comments
- [Introducing Postgres Query Insights in ClickHouse Cloud](https://daily.dev/posts/introducing-postgres-query-insights-in-clickhouse-cloud-yy9pc9sbl) · ClickHouse · 5 upvotes · 0 comments
- [How Five PostgreSQL Optimizations Sped Up Our Dashboard](https://daily.dev/posts/how-five-postgresql-optimizations-sped-up-our-dashboard-u70uete9w) · GitGuardian · 40 upvotes · 0 comments

---

Tags: [#database](https://daily.dev/tags/database), [#postgresql](https://daily.dev/tags/postgresql), [#observability](https://daily.dev/tags/observability)

[View this post on daily.dev](https://daily.dev/posts/dasha-1-8-index-recommendations-i-o-analysis-schema-checks-and-log-insights-ugyubqr7o)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Dasha 1.8: index recommendations, I/O analysis, schema checks and log insights","url":"https://daily.dev/posts/dasha-1-8-index-recommendations-i-o-analysis-schema-checks-and-log-insights-ugyubqr7o","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/dasha-1-8-index-recommendations-i-o-analysis-schema-checks-and-log-insights-ugyubqr7o"},"datePublished":"2026-09-29T07:23:48.035Z","dateModified":"2026-09-29T07:24:10.886Z","description":"Dasha 1.8, an open source read-only performance dashboard for PostgreSQL fleets, adds several major features: automatic index recommendations built from...","image":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","thumbnailUrl":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","isAccessibleForFree":true,"articleSection":"PostgreSQL","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"PostgreSQL","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/8dab534748a94108858df41b7ef7fe86","url":"https://daily.dev/sources/postgres"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/dasha-1-8-index-recommendations-i-o-analysis-schema-checks-and-log-insights-ugyubqr7o","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"database,postgresql,observability","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"PostgreSQL","item":"https://daily.dev/sources/postgres"},{"@type":"ListItem","position":3,"name":"Dasha 1.8: index recommendations, I/O analysis, schema checks and log insights"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/dasha-1-8-index-recommendations-i-o-analysis-schema-checks-and-log-insights-ugyubqr7o#faq","mainEntity":[{"@type":"Question","name":"What new features does Dasha 1.8 add for PostgreSQL monitoring?","acceptedAnswer":{"@type":"Answer","text":"Dasha 1.8 adds automatic index recommendations derived from pg_stat_statements and auto_explain plans, an I/O analysis page built on pg_stat_io for PostgreSQL 16 and newer, 17 schema checks for structural defects such as sequences near exhaustion and tables without primary keys, and log insights integrating with OpenSearch, Elasticsearch, VictoriaLogs and Yandex Managed PostgreSQL. It also adds a read-only MCP connector with 31 diagnostic tools for AI assistants. Teams tracking new PostgreSQL tooling releases can follow updates like this one on daily.dev."}},{"@type":"Question","name":"What PostgreSQL version is required to use the I/O analysis page in Dasha?","acceptedAnswer":{"@type":"Answer","text":"The I/O page requires PostgreSQL 16 or newer because it is built on the pg_stat_io view, which was introduced in that version. Server I/O is broken down by backend type, object and context (normal, vacuum, bulkread, bulkwrite), with WAL breakdown available on PostgreSQL 18. Dasha itself supports monitoring clusters running PostgreSQL 14 through 18. Engineers planning a PostgreSQL upgrade can track version-specific feature gaps like this on daily.dev."}},{"@type":"Question","name":"What permissions does a monitoring tool need to connect to a PostgreSQL cluster without installing an agent?","acceptedAnswer":{"@type":"Answer","text":"A read-only role with the pg_monitor privilege and CONNECT access on every monitored database is sufficient for agentless PostgreSQL monitoring. This approach, used by Dasha, requires no agent or extension installed on the database hosts beyond ones already present, such as pg_stat_statements for query statistics and optionally pgstattuple for bloat analysis. Developers weighing agentless database monitoring setups can compare options on daily.dev."}}]}
```

