TimescaleDB Models
TimescaleDB is our preferred Output of choice when storing your CGNAT logs in a time-series database.
A lot of effort has gone into the data modelling and figuring out the right compression policies to get the most out of the underlying storage.
You can view the data models here on the GitHub repository
These data models can also be used in other databases but you will need to translate the model to the relevant format, eg. using the influx line protocol when using influxdb.
The 4 main models are as followed:
NATSessionMapping- Typically describes a CGNAT Subscriber session with a translated IP and port (aka Port Address Translation / PAT)
NATAddressMapping- Typically describes a CGNAT 1:1 translation
NATPortMapping- Typically describes the same as a
NATSessionMappingbut excluding the destination IP and port
- Typically describes the same as a
NATPortBlockMapping- Typically describes a port block assosication (typically referred as Port Block Allocation / PBA )
All of these models inherit the base MetricBase, an output should ideally implement logic to handle all 4 of these data models when requested to process a metric.