DB
Stream Monitor uses a database to store the monitoring data. There are 4 operational modes, each of which is suitable for different scenarios
None
No database is used. This mode should only be used if all you need is to monitor some live stream events and do not want to use memory or write to the disk.
Pros:
- Simple setup
- Low CPU and RAM usage
Cons:
- Limited functionality
- No data persistence
- No geospatial information (for KLV metadata)
Memory Mode
Data is stored in memory rather than a real database. This mode is useful if data persistence isn’t needed, or if you want to avoid disk writes and have sufficient RAM.
Pros:
- Simple setup
- Low CPU usage
- Fast query performance
Cons:
- Limited functionality
- No data persistence
- No geospatial information (for KLV metadata)
Internal File-Based Database
Data is stored in a file on disk. This mode is ideal for simple setups, handling a small number of channels, and retaining data for short time periods.
Pros:
- Simple setup
- Low RAM usage
Cons:
- Performance degrades as the file grows
- No geospatial information (for KLV metadata)
InfluxDB Database
Data is stored in an InfluxDB database, which enables the benefits of a time-series database, such as easy integration with other systems and geospatial data storage for KLV metadata.
Pros: - Low RAM usage Cons: - More complex setup, requiring additional software and configuration - Performance may degrade over time as data volume increases