The power of Servergraph is that it provides a data exploration experience that can be defined for any user based on their needs and/or their expertise. Below is an example of how easily you can provide this information to your team, management and users.
In this specific instance we'll assume you're building a Servergraph experience for your manager, Ellen, the Directory of IT Infrastructure. Ellen has been working in technology for many years and has a great depth of knowledge and wisdom, but now spends more time dealing with budgetary issues than signing on to systems. But she doesn't want to log in to systems and run commands, she needs quick answers at a high level on usage trends to plan for the future and the general health of the enterprise. She doesn't want to call her admins every time she needs an answer to a question, and in any case she wants to see the facts with her own eyes using her own tool. Rocket Servergraph is perfect for her.
Now she could do this environment up herself, but we'll assume she's busy and you are doing this for her.
The first thing to do is figure out what data she needs. So after a brief discussion you make notes of what she wants:
- General Overview of the Dell/EMC DataDomain Storage servers
- But only those in North American Data Centers
- Details of Amazon AWS backups and usage
- Backup overview
- But only cares about the Production Spectrum Protect and Veeam backups, NOT the legacy NetBackup systems used at some smaller offices.
- Ability to focus on Tier1 systems, but needs to see all systems.
Let's go through this process step by step.
Defining the systems Ellen wants to see:
For defining groups or subsets of systems Servergraph provides a utility called "Scopes." Scopes are groups of systems or individual backup clients defined by any criteria you want. In this case we can see that Ellen only wants to see North American servers, and with an ability to focus on Tier 1 and exclude NetBackup systems.
Assuming what Ellen wants to see is what other's will also want to see, we'll create the following scopes:
- We'll pick and choose all of the nodes that your company defines as "Tier 1." It doesn't matter what backup system these clients are serviced by. We'll assume the NetBackup systems are not Tier1, as they are considered "legacy." But we could define this differently or name it differently.
- Simply choose the DataDomain servers at North American data centers. If there is a naming convention or some other means of identifying them, you can do this via dynamic rule so that any new systems added are properly categorized. i.e. "IF NAME LIKE 'NA*'
- This scope can be created by choosing all the Spectrum Protect and Veeam servers, or by creating a rule that dynamically includes all servers that are NOT NetBackup.
The above scopes will be available to everyone. For general practice you may want to make other complementary scopes for admins to use, like:
Creating a List of Dashboards for Ellen
Now that you know what Ellen wants to see, explore Servergraph and follow the workflows to find the proper dashboards. Note the dashboard names. When you have your list, create Ellen's user.
- From the Servergraph Admin console, choose the "Users" management icon and create a user for Ellen. Quite often this will follow the same format as you use for your Windows Active Directory (AD), particularly if you are using AD for Servergraph access management.
- For Ellen, giver her access to the dashboards you have chosen.
- Select the scopes you have created for her.
Introducing Ellen to her customized Servergraph experience
At this point you need spend 5 minutes showing Ellen what you have created for her. She can login, see only those dashboards she cares about, and select the Tier1 servers only or the backup systems she cares about.