![]() ![]() Use a pie chart if displaying the entire composition for a defined field. For example, if the data is trending over time, line charts or columns charts work well. ![]() When choosing a visualization for a panel, pick the one that best displays the data. If adding legends to visualizations, adjust the placement as well as try to keep the legend keys short, so that they are able to display without ellipses.Add descriptions under single values if it adds value or context.Consolidate the rest of the panels and reorganize dashboard structure to remove excess white space. Combine any duplicating information and remove redundant visualizations.This dashboard has titles on every panel and labels mostly, but use legends when appropriate.There are two separate tables that could very easily be displayed as one table.This entire dashboard is essentially different visualizations for the same data, except for the last table.There are multiple pie charts displaying Last Month and This Month data and then subsequent column charts with the exact same information. Don’t have multiple panels displaying the same thing.It is recommended to use sentence case for descriptions and labels (ie: These are some good looking dashboards!). Titles should also be short and to the point. On the topic of adding titles, it is recommended to use title case for dashboard, panel, or element titles (ie: Capitalize the Important Words). My personal preference is to create the necessary documentation at an external location and add the link to the dashboard. Providing additional documentation with references, such as contacts and field definitions, can be extremely helpful these can be added in an HTML panel within the SimpleXML dashboard. are all a user’s best friend when trying to understand a dashboard. If the visualization seems buggy, it’s good to either fix the issues or make it known that it might not render properly on certain browsers. If there are any custom visualizations being used, it’s a good idea to open the dashboard on various browsers and change the screen size to ensure that the layout doesn’t change. Keep the most important information at the top and related information together. Dashboards only need to display necessary information to the use case. The dashboard should be built for the use case, and nothing more. Just follow these layout and design guidelines and everyone should get along just fine. It would be amazing to have a standard dashboard template for various teams or various use cases, however, no two use cases are ever really the same. When using REST API to query dashboard configurations, it will use the id, not the dashboard title, so keep that in mind when naming, as well. This is most definitely not a best practice! Make sure you keep your ids unique! If multiple dashboards exist in the same app space with the same id, even when the app title differs, an issue arises where changes made in either dashboard are saved in both dashboards. Either keep _clone at the end of the id or replace it with _v2, your username, or something similar. Implementing a naming convention can make it much easier to find dashboards, and to add dashboards to the navigation app bar.Īnother thing to keep in mind is when cloning a dashboard, remember to keep the id unique. One naming standard could be to begin the id and name with a unique identifier, such as the team, customer, or tool the dashboard is for. Let’s hop to it! Naming Standardsĭashboards have both names and ids, it is best to have a naming convention for the id, and if possible, the name. We’re going to dive into some important topics regarding the best practices when creating and maintaining a dashboard. If running Splunk Enterprise version 8.x and above, there’s even a cool Splunk Dashboards app to check out that allows for even more features and utilizes JSON over SimpleXML. If more in-depth customization is required, that can be done through the SimpleXML using HTML panels, in-line CSS, or by uploading a new app from Splunkbase or custom JS/CSS. The creation of a dashboard is incredibly simple and can be done all through the UI. They are incredibly versatile and customizable. So you want to build a better dashboard, do you? Well good, you’ve come to the right place! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |