After two weeks of brainstorming, we have finally migrated:
- 7 #postgresql databases
- with #timescale hypertables
- used by #zabbix
- 1.8TiB
- 5 minutes of downtime
Some databases didn't have hypertables on the source but we needed them on destination.
The workload is now manageable for those databases π
Don't forget to enable and configure Timescale from day 1 if you setup Zabbix running on PostgreSQL. That will be way easier than doing afterwards ππ»
https://www.zabbix.com/documentation/current/en/manual/appendix/install/timescaledb
#postgresql #timescale #zabbix
We may once again be tasked with scraping/polling data off of a slow scientific "big data" database and into #Timescale for a smoother live plotting experience in #Grafana
You'd think CERN would use a dedicated time series store for monitoring data but no, its HDFS+Spark??
The kind of system that, when you ask people about, will say "Oh no I've managed to avoid worrying about it until now" and "It works if you're patient".
We'll give them a taste of sub-second query times~
Recently, we have discovered that some #zabbix databases running on #postgresql were maxing i/o capacity.
We have found out that the housekeeping job, responsible of removing old metrics, was responsible of thousand of DELETE queries. Enabling and configuring #timescale (via Zabbix config) drastically reduced the pressure.
How? By dropping chunks (partitions) instead of deleting rows one by one.
https://www.zabbix.com/documentation/current/en/manual/appendix/install/timescaledb
#zabbix #postgresql #timescale
Slighlty disappointing to see #Influxdb 3's release saying it's "45x faster than Open Source" (referring to the Influx OSS version), and moving to a fully cloud-hosted system... And yet another rewrite, of course.
#timescale's TSL license feels more sensible, keeping the code open source and usable. We think they found a sustainable middle ground for their software, especially compared to what Influx just did.
Corinne Grac presenting first year achievements of WP1 « #Timescale and the role of #ecological #successions in #wetland #restoration » involving @geobiodiversity @LOEWE_TBG @KTheissinger #Daugavpils university and #CNRS #Strasbourg labs
#timescale #ecological #successions #wetland #restoration #daugavpils #cnrs #strasbourg
Let's say I have a bunch of #TimeSeries data events (home, power, temperature,β¦), what's a good place to put them? Is there a cheap managed service or will I need to set up some sort of #Timescale, #Grafana thing myself?
#TimeSeries #timescale #grafana
It's intriguing that #PostgreSQL is both popular and underrated. Many people use it because it's for free, not knowing its superpowers.
I decided to explain why #PostgreSQL is so special, explaining the use case of Fleet Management and how it can help together with plugins like #Timescale and #PostGIS to build the real platform that detects the anomalies and pushes the notifications through #dotnet application to #React app!
https://event-driven.io/en/postgres_superpowers/
Feedback is more than welcome!
#postgresql #timescale #postgis #dotnet #react
Let's rock, day two of @JavaLandConf just began with a welcome and the session of @noctarius2k about #postgresql and #timescale
On yeah, after two days of hard work, we successfully upgraded #PostgreSQL 12 with #Timescale 2.0.1 to PostgreSQL 15 with Timescale 2.9.1, on a test vm and in production π The procedure we produced for it is pretty heavy...
@The_Colbobs
'#NuclearWaste is a resource that can be utilised' - Is this a JOKE?
Nobody's utilising it. Nobody knows what to do with it. Everybody's trying to BURY it.
The human and environmental costs of a #NuclearAccident by faulty design/human error/act of God, are unacceptable. The #EconomicCost of building/removal is unacceptable. The #timescale of #degradation is unacceptable.
Building something that dangerous without knowing how to deal with the known effects is madness.
#nuclearwaste #nuclearaccident #economiccost #timescale #degradation
What database do you use for #timeseries? We use #timescale at work and it's not great π«€
Guess I will do a #fediverse #introduction just like everyone else. My name is Nick, I am currently working on Observability tooling at #timescale. I am into a lot of things mainly Linux, Kubernetes, Music (Jazz/Rock), Vinyl (mainly trying to find weird Japanese Jazz records), Tech and a lot more. I like I say I know a little about a lot of stuff. #mastodon feels new, but also old school at the same time. I hope to toot more here than I ever did on Twitter.
#fediverse #introduction #timescale #mastodon