Kpow v90.6 introduces a new Dark Mode UI, improved intellisense, and confiugrable persistence settings.
Dark Mode
Start the new year right with the sleek new Dark Mode UI available in Kpow v90.6!
Improved Intellisense
From kJQ filters to Schema Editing, text entry input in Kpow has upgraded intellisense for JSON and EDN data.
Persistence Mode
Powered by two internal Kafka Streams applications, Kpow stores data in the first cluster in your configuration (we call this the Primary Cluster). This storage takes the form of several internal topics that are tuned to retain only a small amount of data.
In addition, an audit log topic is persisted permanently for data governance purposes.
These internal topics provide considerable feature support to Kpow, but there are circumstances in which you might want to turn them off.
Kpow v90.6 introduces a new PERSISTENCE_MODE environment variable that provides the following options to tune data storage:
Persistence Mode: Full (Default)
PERSISTENCE_MODE="full"
full is the current persistence behaviour of Kpow and utilizes the full set of internal topics.
This is the default behaviour of Kpow where no configuration is set.
Persistence Mode: Audit
PERSISTENCE_MODE="audit"
audit is a new persistence mode where the only internal topic that is created is the audit log.
This mode considerably reduces the amount of data written to Kafka, while retaining a full data governance trail.
When this mode is activated, certain features of Kpow run in a modified manner:
- Metrics charts are not re-hydrated on a Kpow restart (normally they hydrate from an internal changelog).
- Activity metrics (e.g. 'this topic was written to 3 minutes ago') are not persisted/maintained through a Kpow restart.
- Kpow Streams Agent integration is disabled
Persistence Mode: None
PERSISTENCE_MODE="none"
none is a new persistence mode where zero data is written to Kafka.
This mode ensures that no internal topics are created and no data is written by Kpow to your Kafka cluster.
When this mode is activated, certain features of Kpow run in a modified manner:
- Metrics charts are not re-hydrated on a Kpow restart (normally they hydrate from an internal changelog).
- Activity metrics (e.g. 'this topic was written to 3 minutes ago') are not persisted/maintained through a Kpow restart.
- Kpow Streams Agent integration is disabled
- Audit log and user log are not available
- Staged mutations are not available
- Bulk actions are not available