Topic Disclosure:

1. **What is TimescaleDB, and how to cook it? What kind of tasks would it be good for?**
1. TimescaleDB core concepts. How does it work as an postgresql - extension, which benefits does it give (ex. makes it possible to manage data/metrics with the usual SQL-queries). Which mechanisms does it have (space/time partitioning, chunks, hypertables data compression and retention, etc.). Configuration differences (singlenode/multinode setup)
2. More specific about singlenode/multinode setups. What is promscale and how does it work in pair with TimescaleDB?
3. What cases are most suitable for specific TimescaleDB setup?
2. **Choosing configuration and infrastructure for TimescaleDB**
1. Best Practices for System Deployment
2. High - available setup: Patroni + AccessNode + Datanodes + Kubernetes
3. Recommended parameters for VM’s and Databases. Postgres/patroni configuration (shared memory/wal params etc.). CPU/RAM/Disks etc.
3. **What to monitor?**
1. Key metrics to pay attention to (basics and specific for tsdb)
2. Which exporters and dashboards do we need?
4. **What to monitor?**
1. Key metrics to pay attention to (basics and specific for tsdb)
2. Which exporters and dashboards do we need?
5. **Troubleshooting from console**
1. Useful sql - queries and utilities, that may help you
2. Applying it in action. Production cases
6. **Advices and our own experience with mistakes**
1. When to add resources and when to tune the software itself?
2. TSDB/Patroni/Promscale wins & failures