Squared Up displays performance metrics as graphs, sparklines and bar charts. To show these performance metrics, Squared Up connects to the SCOM Data Warehouse using its IIS application pool identity.
Following installation the setup wizard auto-configures the Data Warehouse connection for you. It picks up the Data Warehouse location from SCOM, and then gives the Squared Up application pool account the correct permissions by giving the account a SQL server login with the OpsMgrReader role for the Data Warehouse database.
If graphs are not shown in Squared Up, then you should check the Data Warehouse connection.
There are two parts to the Data Warehouse connection: Firstly, the Data Warehouse server name connection in Squared Up. Secondly, permissions, i.e. the SquaredUpv4 application pool account having the the OpsMgrReader role for the Data Warehouse database.
Log in to Squared Up as a SCOM admin user, who is also a SQL sysadmin for the Data Warehouse database.
Click on the right-hand menu ☰ then system and then the Connections perspective.
In the Other Connections section check that the Data Warehouse server name is correct. If it is wrong, edit it and click apply changes.
On the Squared Up server log in to Squared Up as a SCOM admin user, who is also a SQL sysadmin for the Data Warehouse database. If the user you are logged in as does not have SQL sysadmin permissions then you may need to Configure the Data Warehouse permissions manually
This gives the application pool identity a SQL server login with the OpsMgrReader role for the Data Warehouse database.
When using Windows authentication this step must be carried out on the Squared Up server.
Check that graphs are shown in Squared Up, for example on a server page. You may need to wait a few moments and refresh the page.
If performance graphs, sparklines or bar charts are not shown, you may need to Configure the Data Warehouse permissions manually.
If you still experience problems see the article Troubleshooting The Data Warehouse Connection.
The Squared Up web server needs to make a network connection to the SCOM Data Warehouse server on port 1433. If you have a firewall then you may need to configure it appropriately. See Which ports do I need to open in my Firewall?