I must say I am pretty happy with the backup solution here. It took a few years to find a setup I am happy with, but this one works:
- Storing important files and data on the Synology DS1515+, with ca 8 TB disk (effective raided size) and 2 SSD drives for cache. Using WD Red 5TB SOHO NAS SATA-600 drives as main storage.
- Using CrashPlan to add another layer of off-site backup for data on the DS1515+.
- CrashPlan running on the DS1515+ also receives backups from a bunch of other computers, but around here and for friends and family.
Qlik Sense is pretty cool. Ok, it’s early days and they are still on version 1.x, but still – lots of potential there.
And the name is kind of neat too – Qlik’s marketing people must have had a long hard think before settling on “Sense” for their next gen product… There are just so many puns and word games that keep popping up.
Sense did however give us a good laugh the other day. Trying to open a Sense app that was developed some time ago, we got this error message. Now that’s pretty funny..
Slack has only been around since August 2013, but I would definitively say it’s one of the better team communication services out there. The web client is great, and the OSX and IOS clients are truly awesome. It integrates with tons of other services, including Dropbox, GitHub, IFTTT, Jira, Google Drive, RSS, Nagios, Yo, Twitter and Pingdom are just some of the services it supports (as of today they seem to support ca 75 integrations). There are also generic connectors for incoming and outgoing webhooks, especially the incoming webhook feature will be interesting from a systems monitoring perspective – it will allows us to post messages to Slack by just calling a certain URL.
In this post we will look how we can use this to both monitor the various QlikView services, as well as monitor the transfer of files (e.g. data files used by QV) to a QV server, and a as a generic way of sending notifications from QlikView Management Console (QMC).
Most of the concepts below also apply to Qlik Sense, of course.
Node-RED flow for controlling a Blink(1) USB indicator light
Node-RED is a truly awesome framework for visually building data flows. There is a lot of focus on wiring together hardware devices and Internet of Things, but there are also plenty of modules for connecting to email, social media, various online services etc.
After using it during some months I can confirm that stability is absolutely fine, don’t think I have had a single issue with the setup due to Node-RED itself.
Version 0.10.1 came out a week or so ago (early Feb 2015) and brought things like better partitioning of flows in the form of subflows, improved Raspberry Pi support, binary MQTT payloads to name just a few of the improvements.
I am running Node-RED on an always-on Mac, running latest OS X. This machine is very stable but for various reasons I do need to restart it every now and then. It would then be very nice to have Node-RED start automatically at boot. That’s somewhat complex to do, but having an app starting at login is trivial – let’s do that instead. I am always logged into this computer anyway, so it won’t be a problem.
Let’s try an experiment.
I have set up a questionnaire that anyone can fill in and submit.
There you can add working and non-working memory configurations for your Synology NAS. Ideally this will enable people to increase the memory in their NAS:es without lots of trial and error on what memory works in what NAS models – or spammers will fill the document with crap data… Time will tell.
Background is that I started a similar effort here on the blog, but Google Forms are way better for this, so let’s use that instead.
Let’s go – don’t be shy!
Update: Let’s work together and capture data on what memory modules work, and which don’t, on the DS1515+ and other Synology NAS models!
As noted in a previous post, a new Synology DS1515+ NAS landed here the other week. It’s a very nice products in most respects, but a couple of rather annoying details bring the overall impression down – more on that in a later post.
The DS1515+ ships with 2 GB of RAM, with an extra, empty memory slot available for memory upgrades. 2 GB is really on the low side if you intend to run additional applications on the NAS. CrashPlan for example is built on Java, which is pretty resource hungry to begin with, then the memory consumption goes up with the number of files backed up.
Synology specs tells us that a 4 GB SO-DIMM can be added, for a total of 6 GB. Stories from the Synology forum however indicate that it is quite possible to replace both the internal (some disassembly required, probably voiding warranty..) and user accessible RAM modules, for a total of 16 GB RAM.
With a bunch of different SO-DIMM modules in the drawers here, let’s test them to see which ones can be used with the DS1515+ and which ones cannot.
A great feature of Qlik Sense is that your ETL/load script scripts can be moved over from existing QlikView apps with very few modifications. Basically, you need to change the data sources to Sense’s way of doing things* (which I would say is a lot more robust and flexible), then things are likely to work straight off the bat.