From 55e3b889f61d3685b1e75fd6599eaf5f482de201 Mon Sep 17 00:00:00 2001 From: Sterling Hammer Date: Thu, 9 Nov 2017 17:00:18 -0600 Subject: [PATCH] Update setup.md Updated bad links. - Screenshot link file extension case - \ instead of / for Get-DeploymentGuid.ps1 --- docs/setup.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/setup.md b/docs/setup.md index 70da301..8f94056 100644 --- a/docs/setup.md +++ b/docs/setup.md @@ -38,9 +38,9 @@ To deploy a usage collection VM on an Azure Stack: 7. In **Template**, paste the content of **azuredeploy.json** which can be found [here](../template/azuredeploy.json) into the text box before clicking **Save**. 8. Fill in the parameters according to instructions that appear in the tooltips. -![template tooptips](screenshots/template_description.png) +![template tooptips](screenshots/template_description.PNG) -Note that some fields may be pre-populated to a default value, always double-check the pre-populated value descriptions to make sure it is applicable to your deployment. To obtain the deployment guid for an ASDK, open PowerShell on the host machine, and run [Get-DeploymentGuid.ps1](..\Get-DeploymentGuid.ps1). +Note that some fields may be pre-populated to a default value, always double-check the pre-populated value descriptions to make sure it is applicable to your deployment. To obtain the deployment guid for an ASDK, open PowerShell on the host machine, and run [Get-DeploymentGuid.ps1](../Get-DeploymentGuid.ps1). Note to get the DeploymentID (GUID) on multi-node Azure Stack deployments, you must connect to the Privileged Endpoint using a PS-Session and execute the Get-AzureStackStampInformation function. Copy the value in the first parameter returned which is DeploymentID. 9. Use the Default Provider Subscription, create a *new* resource group, and pick a location before hitting **Create**. @@ -157,4 +157,4 @@ For specific documentation on the Power BI dashboard template, refer to the [das ## Limitations 1. As of 8/9/2017, there is 8mb size limit on the request that PowerBI uses to fetch data from OMS. This restriction is planned to be lifted in the future by the OMS Log Analytics team, Yammer thread is linked here: https://www.yammer.com/azureadvisors/threads/924427094 (In OMS Log Analytics Upgrade Private Preview group in Azure Advisors network). -2. If the restriction persists, one way to increase the number of days of usage data available (by 24x) is pull in daily aggregated usage data from OMS instead of hourly aggregated data. The obvious drawback for this method is that one will not be able to drilldown to the hourly level on the PowerBI dashboard. \ No newline at end of file +2. If the restriction persists, one way to increase the number of days of usage data available (by 24x) is pull in daily aggregated usage data from OMS instead of hourly aggregated data. The obvious drawback for this method is that one will not be able to drilldown to the hourly level on the PowerBI dashboard.