This example is extracted from a long-running installation. The purpose is to have a simple monitoring of several servers at a rather primitive level. Just slightly more intelligent than a raw PING. But still easy to integrate. It avoids the overkill of information you are often confronted with while you are just interested in the number of active process or similar basic figures.
It's been 6 weeks since my original article - - - - -but I have been busy on this project
I have been looking at/thinking about a replacement for ZEN for around 12 months but only really started in depth 4 months ago. Also been in IT for long enough that I can "get a feel" for a product/technology and make decisions accordingly without going into great detail. Any new technology has a learning curve and I don't want to waste time and effort on something that won't fly. And, as always, I am looking to minimise the learning curve as I want to concentrate on delivering business benefit.
I'm using Git with DeepSee and when I need to do a commit to the git repo I'm exporting ALL the pivots and dashboards from the namespace. But I can forget to do that) And it can take time for a large system.
What is the way to manage automatical export of DeepSee artefacts which we are editing in UI (Cubes, Pivots, Dashboards, Pivot Variables, Term lists, Shared Measures) into files every time when I push Save button?