Memory

The Exot Inspector package incorporates a built-in memory store (RAM), which is typically sufficient for most development and debugging purposes. However, it’s essential to note that any data stored in this memory will be lost upon restarting or stopping the process.

Configuration

• evictionInterval: number: Specifies the interval for running expired data eviction (in milliseconds, default is 5 minutes).
• maxEntries: number: Defines the maximum number of entries per key.

Expired Data Eviction

The memory store automatically deletes expired data upon access or at configured intervals (refer to evictionInterval).

During eviction, the procedure scans all entries in the store and removes those that have expired. It’s advisable not to set evictionInterval too low, as this may impact the performance of your application, particularly concerning the volume of data.

Maximum Store Size

By configuring the maximum number of entries using the maxEntries parameter, you gain control over the size of the store, irrespective of the frequency of writes into the store.

When this limit is reached, the memory store systematically removes the oldest entries. It’s important to note that this configuration parameter applies per key, meaning it restricts the number of entries a single key (or metric) can possess.

Persistent Stores

For integration with persistent stores, you can utilize one of the supported databases:

• Redis