bodach
November 1, 2021, 11:10am
1
Hello,
I saw this gauge chart somewhere and I want to use the same structure in my canvas. Any ideas where can i download it?
That one looks custom made, so you could make the same as well. If you manage to remember where you found it and it's an Elastic post, let me know and I can contact the author to get it.
bodach
November 1, 2021, 12:55pm
3
Thanks for the fast reply, I found it on :
opened 11:23PM - 07 Apr 20 UTC
enhancement
Team:Presentation
impact:high
Feature:Canvas
Many Kibana users are using Kibana to monitor their infrastructure and services.… We want to provide them a quick out of the box way to create Observability Canvas which shows in a pixel-perfect way an overview of their infrastructure health. The workpad can then be proudly presented on a large monitor and display health info and support our Observability users better. The way we plan on achieving this is by new observability template in Canvas.
Desired outcome:
- In a few mouse clicks, users will get beautiful Observbility Canvas workpad based on their real data.
- By default, the elements will point to generic indices names (filtebeat-*, metricbeat-*). The structure of the beats indices is familiar and the fields used will be ECS fields.
- Easy way to change the index pattern that the Canvas workpad will run on
- A discoverable solution that will help users find the template
- Ability to set customize Workpad in a few minimal steps instead of creating something from scratch which will take users more time. The workpad can then be tweaked by the users based on their needs and provide a more advanced way to start their Canvas workpad.
Open questions:
- Observability works mainly with Beats. Canvas doesn’t have the concept of index patterns. How much does that present a challenge?
- Observability usually uses multiple indices, what to show when users don’t have metrics or heartbeat?
- There is an ongoing initiative for new sample data in Kibana. Should we combine this effort? Personally, at first, I thought we should, thinking about it again and since the template needs to be available for users with and without sample data I think its better to separate these two initiatives. Open to discuss if someone thinks otherwise
Suggested MVP1:
- Designed Workpad with one page with key observability metrics based on ECS fields.
- Second workpad page consists of instructions on how to replace to the right index
- Users can manually change to their own data by changing every element
- By default different elements refers to real indices for example `filtebeat-*`
- In case there is no index that matches the users' cluster, and the element returns an error, the template will print meaningful message so users know they need to change to their real index. That is to avoid a situation when users choose the template and get a page full of errors which can be a frustrating experience
Example :
![image](https://user-images.githubusercontent.com/32550316/78727264-041ddb00-78e9-11ea-8574-eb836ed25aea.png)
All elements point to generic indices names which their structure is known (example `filebeat-*`)
![image](https://user-images.githubusercontent.com/32550316/78727694-3ed44300-78ea-11ea-92b2-57433e151f3f.png)
Next steps:
- [ ] @cyrille-leclerc can you and the observability PMs guide us on the more important metrics to include?
- [ ] Design/creative services help to make Observability workpad amazing
- [ ] Canvas engineer to come up with MVP flow and work needed to support. As the first step, we can add it as another template in Canvas. The main limitation is discoverability there might be other technical challenges
cc: @timductive @poffdeluxe @shaunmcgough @crob611
I am having someone looking into this to see if they can find the original workpads for that. I'll update here when I hear from them.
1 Like
system
(system)
Closed
November 29, 2021, 6:42pm
5
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.