There's no kind of cohesive overarching theme to this dashboard. The amount of information in the custom chart is just too volumous. It's just too busy and doesn't show the details necessary. This is actually a horrible dashboard example for most people. I never said it was going to be a good dashboard example. I wanna go ahead and show you a dashboard example. So you don't get a lot of scope creep on either sides and the dashboard is built exactly as needed for the intended audience. You have to have the answers to before you can actually start building these dashboards 'cause that'll help you kind of build a scope in place. Or is it gonna be embedded in another source? So people can see it somewhere else. So is it going replace an existing thing? Is it going to be used for trouble tickets? Is it displayed in a dark NOC? You know, how's it gonna be used in the environment? And last but not least, who is gonna be seeing this? Whether it's someone consuming it, in like I said, a NOC or whether it's gonna be the first page they land on when they log in to Orion. You need to understand how the information is going to be used. Everything is not a viable answer and everything dashboard is garbage and no one will be able to use it because it's too busy. There's only one thing I'm gonna say here. So you need to have a sit down with those teams, first and foremost, you need to find out what information is most important to them. And although that may be true in its purest sense, the information that people want on that dashboard comes from these other teams. When we talk to customers about dashboards, whether it's on THWACK or at an in-person event, we get a lot of kind of pushback on this because people think dashboards are built necessarily by the IT person or the monitoring person for the teams. So go ahead and bring that out, but I'll show it to everyone anyway. If you already followed along with Lab 86, great, you probably already have this query somewhere in your Notepad somewhere.
#Orion solarwinds api windows#
In our last session, this is the query we started with, where we wanted to get a list of Windows nodes that are currently up and only return the caption, IP address, uptime, CPU count, sorted by the CPU count descending, and then uptime descending. Strings are defined by single quotes and comments are defined by double dashes. So the same wildcards you use, the percent sign and the underscore and we support select queries only. SWQL is very much like SQL in the fact that it uses a lot of the same techniques. If you're familiar with SQL Server Management Studio or SSMS, it basically looks and behaves very similarly.
#Orion solarwinds api download#
Today, for my examples I'm gonna use SWQL Studio, which you can download as an MSI file from GitHub under the Orion SDK releases. What it is is essentially a selectable SQL-like environment and language that you can use to interface directly with the data behind the SolarWinds API. Back in Lab 86, I talked about SWQL or the SolarWinds Query Language, and I wanted to make sure I touch very briefly on it here. So you build the proper dashboards for their usage and also where to find more help, if you get yourself stuck.
#Orion solarwinds api how to#
How to actually have good conversations, research, design sessions with your teams. What makes it good or a bad dashboard, how to build your own widgets in the Orion Platform. So I wanna talk about how it gets started with dashboards. So there's several things we're gonna cover today, but I wanna start with kind of a quick agenda overview. How do you use your custom queries? How do use your custom widgets? How to build reports and things you need to build dashboards that can make actionable decisions for your organization. If you haven't already watched the 101 session, I encourage you to go back and look at episode 86, where I go into detail about that, but today's really gonna be all about dashboards. I'm your host today, Kevin Sparenberg, and today we're gonna be doing our SolarWinds Orion API 201 session.
A working knowledge of basic T-SQL queries is highly recommended. Kevin will show you how to represent existing data from within your monitoring ecosystem using traditional elements (e.g., reports, widgets, etc.) and in the new, modern dashboards, as well. Sparenberg, technical content manager for Community, will continue with his deep dive into the SolarWinds Query Language (SWQL). In this follow up to " Orion SDK 101: Intro to PowerShell and Orion API," Kevin M.
0 kommentar(er)
