Lasso¶
A Lassoreport is the first step of any evaluation and assessment process delivered by EDB on existing installations of Postgres or related tools,including supportability checks , health checks ,and incident response investigations.
You can generate it both in an _automated_
and in a _supervised_ way.
Some information can be gathered through automated tools in a noninvasive way, in phase 1 of the Lasso report. Some other information isn’t automatically detected (at least in a noninvasive way). You must communicate it as part of the Lasso report, in phase 2.
After you return the gathered information to EDB engineers in phase 3, EDB proceeds with data analysis. Then comes either:
An offer, in the case of an initial assessment
A final report assessing the status and the health of your Postgres server, in the case of a health check service
Important
You must provide EDB with all relevant information about the underlying system to check, in particular network and hardware configurations.
- Phase 1
- Phase 2
- Phase 3
- Returning the Lasso report
- Troubleshooting
- What do we gather in our Lasso report?
- Detailed breakdown of gathered data
- GNU/Linux operating system ### barman crontab/cron (
barman_crontab_cron) - Microsoft Windows operating system ### PEM configuration - Windows (
pem_configuration_windows) - PostgreSQL/PGD3 nstance ### Current archiver stats (
postgresql_archiver) - Details for every Postgres/BDR3 database ### PGD1 replication slots (
postgresql_db_bdr1_replication_slots) - Barman (Backup and Recovery Manager) ### Barman check (
barman_check)
- GNU/Linux operating system ### barman crontab/cron (
- Servers accepting upload of reports
