Timescale DB
-
-
The NetXMS database schema is different for TimescaleDB (even from Postgres -> TimescaleDB), so you'd have to use nxdbmgr for the migration. It's meant to support migration to TimescaleDB from 2.2.14 onwards (haven't tried it yet, we're still running load tests and comparisons between TimescaleDB and Postgres, feeding 50-60GB of live data into each system per day to compare performance).
One thing to note on TimescaleDB use, from what I can tell NetXMS configures the Hypertables with a 1 week chunk interval by default. Depending on your data ingestion rate, you may want to change that before you go live (e.g. for our test, I changed it to 1 day). -
-
-
-
@tursiops said in Timescale DB:
The NetXMS database schema is different for TimescaleDB (even from Postgres -> TimescaleDB), so you'd have to use nxdbmgr for the migration. It's meant to support migration to TimescaleDB from 2.2.14 onwards (haven't tried it yet, we're still running load tests and comparisons between TimescaleDB and Postgres, feeding 50-60GB of live data into each system per day to compare performance).
One thing to note on TimescaleDB use, from what I can tell NetXMS configures the Hypertables with a 1 week chunk interval by default. Depending on your data ingestion rate, you may want to change that before you go live (e.g. for our test, I changed it to 1 day).When feeding 50-60GB of data per day , that represent how many devices/instance ?
-
Just want to node that TimescaleDB support in 3.0 is much better then in 2.2.16, and schema is slightly different (including chunk intervals).
Best regards,
Victor -
@idaham said in Timescale DB:
@tursiops said in Timescale DB:
The NetXMS database schema is different for TimescaleDB (even from Postgres -> TimescaleDB), so you'd have to use nxdbmgr for the migration. It's meant to support migration to TimescaleDB from 2.2.14 onwards (haven't tried it yet, we're still running load tests and comparisons between TimescaleDB and Postgres, feeding 50-60GB of live data into each system per day to compare performance).
One thing to note on TimescaleDB use, from what I can tell NetXMS configures the Hypertables with a 1 week chunk interval by default. Depending on your data ingestion rate, you may want to change that before you go live (e.g. for our test, I changed it to 1 day).When feeding 50-60GB of data per day , that represent how many devices/instance ?
That was for testing purposes only. I configured a number of firewalls to generate verbose syslog messages on everything and had them send those to the test system, in addition to creating a range of "poll every 5 seconds" DCIs.
So it was live data, but not something I'd for a live system. Can't really compare that to a number of nodes.As Victor said, TimescaleDB support is much improved in version 3. I'd suggest waiting for the release or upgrading to version 3 (beta version in 'unstable' repository) if you intend to use it now.
I always thought timeseries databases where better suited for NMS's 
Thanks for the infoHello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login