Management tooling

[lukashornych]

To make evitaLab even more useful, we want to add several tools for database server/catalog/collection management.

For management of database server itself we would like to:

• [ ] status 🟢 -> solved in #103

  • URL, version, API URLs, ...
  • evitaDB runtime configuration
  • basic charts? (heap size, cpu usage, ...)

• [ ] logs + filtering 🟢 -> solved in #142

• [ ] JFR tracing (start, stop, download, configuration) 🟢 -> solved in #143

  • optionally embed JFR visualizer if possible

• [ ] create catalog -> solved in #144

Cluster management (in future):

• [ ] health, lags
• [ ] master/replica view

For catalog management we would like to:

• [ ] query recording -> solved in #150
• [ ] time machine 🟢 -> solved in #95
  • catalog version
  • mutation listing with filtering + mutation detail
  • create new catalog from version
• [ ] backup, restore 🟢 -> solved in #147
• [ ] drop 🟢
• [ ] unload?, load?
• [ ] replace, rename 🟢
• [ ] (un)make readonly
• [ ] create collection
• [ ] consistency
• [ ] API compatibility
  • REST
  • GraphQL

Entity collection management:

• [ ] index listing 🟢
  • size
  • consistency
  • recreate
• [ ] drop 🟢
• [ ] rename 🟢

Items marked with 🟢 have API support in evitaDB and can be implemented. Each section/item will be solved in separate issue.

[lukashornych]

Maybe we should introduce connection name into toolbars like so

Lots of these tools work on level of evitaDB server/connection and it could be confusing having connection name only in tab name.

@novoj toughs?

[novoj]

Yes, but there is a lot of data to read, and it would be nice to recognize the right connection from the tab name without clicking on it. What about picking for each connection random color and prepend this bullet before catalog name? And do that only when there are more than single connection? Or use another emoji: 1️⃣2️⃣3️⃣ ... etc? It scales up to 10 connections which seems reasonable enough.

[lukashornych]

After some discussion, we will not render connection name in the toolbars (yet). Instead, we will explore different approach to connections entirely in #149.