Application is slow/getting slower (L2)

What to do if the Reporting Hub application taking longer to load content

Short-term - restart App Service

If you stop and start the App Service, it will clear any cache/memory issues that are causing slowness. This is a quick fix and more data and review is necessary which are explained below.

Longer term

The Reporting Hub application is a combination of a number of Azure services and application code. There are a number of variables that can impact its performance.

Login Slowness

Complex or deep security groups hierarchy

If you're using Azure Active Directory (AAD) and you have a complex AAD security groups hierarchy, you may want to consider switching to "non-inherited" in each Reporting Hub Tenant Admin page. When a user signs in, the Reporting Hub application needs to identify all security groups to which that user belongs in order to present the list of navigation items. If inheritance is enabled on a complex/deep security groups hierarchy. it takes longer for the application to identify all of the groups and present only the authorized navigation items. By switching to non-inherited, only the content directly assigned to the user's security group(s) will be made visible.

All pages take a long time to load

Evaluate custom DNS vs. default DNS

When a new Reporting Hub application instance is created, it is assigned a default DNS (name.azurewebsites.net). A custom DNS is managed by a DNS provider which routes internet traffic to the subdomain you create (example: analytics.yourcompanyname.com). Sometimes the routing adds a delay in getting to the application. To validate if this is adding a delay, compare the time it takes to load a page from the custom DNS to the time it takes to the load the same page using the default DNS. If there's a difference, you may want to review with your networking team or DNS provider. There could be firewall/proxy settings that are causing delays.

Azure resource monitoring

To go further, we recommend configuring a resource monitoring tool, like Azure Monitor, to capture metrics on all of the Azure resources.

The applications to monitor would include the Azure App Service, Azure SQL Database and Power BI Embedded Capacity.

In order to know where to improve your infrastructure, you'll need to gather Azure monitoring data to ensure can isolate the source of the problem and implement the correct remediation.

Update the Reporting Hub to the most recent version generally available

We have made significant improvements to memory management in version 6.5. Prior to this change, we noticed that response times and particularly memory usage on the App Service would gradually continue to increase. The only way to bring it back down was to restart the App Service. The improvements we have made in version 6.5 has reduced the need for restarting the App Service significantly. Many of our customers report not having to restart the app service due to lack of memory availability since they updated.

See below link for how to update your application:

pageSelf-Serve Guided Updates

Application Insights may cause issues while updating. It adds a NodeJS module that causes the update to fail. Please disable Application Insights before updating and you can re-enable it after the update is complete.

Last updated