# Visualisation for back-up jobs

**URL:** <https://discuss.elastic.co/t/visualisation-for-back-up-jobs/202715>\
**Category:** Kibana\
**Created:** [October 8, 2019, 6:53pm UTC](https://discuss.elastic.co/t/visualisation-for-back-up-jobs/202715 "2019-10-08T18:53:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![john.hoogeveen](https://avatars.discourse-cdn.com/v4/letter/j/a9a28c/32.png) [@john.hoogeveen](https://discuss.elastic.co/u/john.hoogeveen)\
**Post date:** [October 8, 2019, 6:53pm UTC](https://discuss.elastic.co/t/visualisation-for-back-up-jobs/202715/1 "2019-10-08T18:53:22Z")

</div>

Hello,

I am struggling with finding a solution to visualize the back-up status of different backup-up applications into one single view.  
Basically we have several customers with different back-up applications that all are using windows eventlog entries. We are processing them with winlogbeat and dissect them with logstash to make standard fields in the index like “backup.custumer”, “ backup.server”, “backup.application”, “backup.type”, “backup.vm” and “backup.status”. This concept works well for our current list of back-up applications and gives us flexibility.  
My current challenge is to visualize this in a single view where my collogues can select a dashboard and see all the latest status for the different customers and back-up applications in this view a bit like below.

![26](https://us1.discourse-cdn.com/elastic/original/3X/4/6/46991580d816b8b33e1487d0a35900fd7b8e8602.png)

The view should sort the “VM backup” per servername and also group them by customer in case a customer has more that 1 back-up solution in their environment.  
The colors reflect the status of the backup job, success warning, error, skipped/none  
They can select a timeframe that needs to be shown, on a daily basis a week view would be fine, for long term reporting it might be like 3 moths in the same view  
For now I am clueless, can somebody point me in the right direction?

Thank you

John

---

<div class="post-metadata">

**Author:** ![markov00](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markov00/32/33316_2.png) [@markov00](https://discuss.elastic.co/u/markov00)\
**Post date:** [October 28, 2019, 10:55am UTC](https://discuss.elastic.co/t/visualisation-for-back-up-jobs/202715/2 "2019-10-28T10:55:34Z")

</div>

I think the best way to handle that is to create a chart in Vega similar to

> **[Editor/IDE for Vega and Vega-Lite](https://vega.github.io/editor/#%2Fexamples%2Fvega-lite%2Frect_heatmap)**
>
> The Vega editor is a web application for authoring and testing Vega and Vega-Lite visualizations. It includes a number of example specifications that showcase both the visual encodings and interaction techniques.

This can give you enough flexibility to handle your case.

---

<div class="post-metadata">

**Author:** ![john.hoogeveen](https://avatars.discourse-cdn.com/v4/letter/j/a9a28c/32.png) [@john.hoogeveen](https://discuss.elastic.co/u/john.hoogeveen)\
**Post date:** [October 28, 2019, 8:24pm UTC](https://discuss.elastic.co/t/visualisation-for-back-up-jobs/202715/3 "2019-10-28T20:24:28Z")

</div>

Thank you for the suggestion, that will be a nice challenge.  
Just leaning Elasticsearch and now Vega but it looks promising 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 25, 2019, 8:24pm UTC](https://discuss.elastic.co/t/visualisation-for-back-up-jobs/202715/4 "2019-11-25T20:24:30Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.