# Designing a visualisation for success/failure of processes

**URL:** <https://discuss.elastic.co/t/designing-a-visualisation-for-success-failure-of-processes/324634>\
**Category:** Kibana\
**Tags:** lens\
**Created:** [February 3, 2023, 10:05am UTC](https://discuss.elastic.co/t/designing-a-visualisation-for-success-failure-of-processes/324634 "2023-02-03T10:05:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![PetervH](https://avatars.discourse-cdn.com/v4/letter/p/9dc877/32.png) [@PetervH](https://discuss.elastic.co/u/PetervH)\
**Post date:** [February 3, 2023, 10:05am UTC](https://discuss.elastic.co/t/designing-a-visualisation-for-success-failure-of-processes/324634/1 "2023-02-03T10:05:46Z")

</div>

Hi

Can someone suggest a way to achieve the following:

I'm getting a constant stream of events from a source. These events include data that specifies whether a particular process has completed successfully, as indicated by the presence of these events:

- Process started successfully

- Process in progress

- Process completed successfully

If the process does not complete successfully, the following events would be sent:

- Process started successfully

- Process in progress

- Process failed

My question is - how can I set up a visualisation(?) in Kibana to display:

- Process number

- Process completed successfully (perhaps with a green button/tick) OR

- Process failed (perhaps with a red button/cross

Thanks in advance  
Peter

---

<div class="post-metadata">

**Author:** ![Marco\_Liberati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marco_liberati/32/82953_2.png) [@Marco\_Liberati](https://discuss.elastic.co/u/Marco_Liberati)\
**Post date:** [February 7, 2023, 10:00am UTC](https://discuss.elastic.co/t/designing-a-visualisation-for-success-failure-of-processes/324634/2 "2023-02-07T10:00:41Z")

</div>

Hi @PetervH

I think a table might help in this case.  
So I built a quick prototype of what I have in mind:

 ![Screenshot 2023-02-07 at 10.57.35](https://us1.discourse-cdn.com/elastic/original/3X/2/e/2eb8cce5d72fac84b878d32b3ce39fe8c6a5c4c2.jpeg)

The tricky bit, I think, is to get right the `Status check` dimension: what I've done is to create a runtime field from the `process.status` field, creating a new `process.status_as_number` field which converts the keyword/string value into a mapped number type (i.e. ok =\> 1, pending =\> 0, fail =\> -1)

At this point use the color by value feature to assign colors to the mapped numeric values of the `Last value of process.status_as_number`.  
What do you think?

---

<div class="post-metadata">

**Author:** ![PetervH](https://avatars.discourse-cdn.com/v4/letter/p/9dc877/32.png) [@PetervH](https://discuss.elastic.co/u/PetervH)\
**Post date:** [February 8, 2023, 7:44am UTC](https://discuss.elastic.co/t/designing-a-visualisation-for-success-failure-of-processes/324634/3 "2023-02-08T07:44:04Z")

</div>

Thanks, Marco. Will give it a try.

---

<div class="post-metadata">

**Author:** ![PetervH](https://avatars.discourse-cdn.com/v4/letter/p/9dc877/32.png) [@PetervH](https://discuss.elastic.co/u/PetervH)\
**Post date:** [February 15, 2023, 1:38pm UTC](https://discuss.elastic.co/t/designing-a-visualisation-for-success-failure-of-processes/324634/4 "2023-02-15T13:38:39Z")

</div>

Hi Marco

I'm assuming I need to use a filter like grok to map all my input fields and then to create the runtime field that you suggested (process.status\_as\_number).

I'd then use an expression to convert the value to a mapped number type.

Finally, I assign a colour to the mapped numeric value.

---

<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:** [March 15, 2023, 1:39pm UTC](https://discuss.elastic.co/t/designing-a-visualisation-for-success-failure-of-processes/324634/5 "2023-03-15T13:39:38Z")

</div>

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