Skip to content

Commit 7d41f3a

Browse files
2 parents 24a0229 + 401569f commit 7d41f3a

File tree

42 files changed

+477
-925
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+477
-925
lines changed

.openpublishing.redirection.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15400,6 +15400,11 @@
1540015400
"redirect_url": "/azure/stream-analytics/stream-analytics-troubleshoot-query",
1540115401
"redirect_document_id": false
1540215402
},
15403+
{
15404+
"source_path": "articles/backup/backup-introduction-to-azure-backup.md",
15405+
"redirect_url": "/azure/backup/backup-overview",
15406+
"redirect_document_id": false
15407+
},
1540315408
{
1540415409
"source_path": "articles/backup/backup-azure-backup-ibiza-faq.md",
1540515410
"redirect_url": "/azure/backup/backup-azure-backup-faq",
@@ -30879,6 +30884,16 @@
3087930884
"redirect_url": "/azure/iot-accelerators/quickstart-connected-factory-deploy",
3088030885
"redirect_document_id": false
3088130886
},
30887+
{
30888+
"source_path": "articles/iot-accelerators/iot-accelerators-connected-factory-sample-walkthrough.md",
30889+
"redirect_url": "/azure/iot-accelerators/iot-accelerators-connected-factory-features",
30890+
"redirect_document_id": false
30891+
},
30892+
{
30893+
"source_path": "articles/iot-accelerators/iot-accelerators-connected-factory-gateway-deployment.md",
30894+
"redirect_url": "/azure/iot-accelerators/iot-accelerators-connected-factory-features",
30895+
"redirect_document_id": false
30896+
},
3088230897
{
3088330898
"source_path": "articles/iot-accelerators/iot-accelerators-predictive-overview.md",
3088430899
"redirect_url": "/azure/iot-accelerators/quickstart-predictive-maintenance-deploy",

articles/aks/coredns-custom.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -190,5 +190,7 @@ To learn more about core network concepts, see [Network concepts for application
190190
[kubectl delete]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#delete
191191
[coredns hosts]: https://coredns.io/plugins/hosts/
192192
193-
<!-- LINKS - external -->
193+
<!-- LINKS - internal -->
194194
[concepts-network]: concepts-network.md
195+
[aks-quickstart-cli]: kubernetes-walkthrough.md
196+
[aks-quickstart-portal]: kubernetes-walkthrough-portal.md

articles/aks/upgrade-cluster.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ To confirm that the upgrade was successful, use the [az aks show][az-aks-show] c
5959
az aks show --resource-group myResourceGroup --name myAKSCluster --output table
6060
```
6161

62-
The following example output shows that the cluster now runs *1.11.6*:
62+
The following example output shows that the cluster now runs *1.12.8*:
6363

6464
```json
6565
Name Location ResourceGroup KubernetesVersion ProvisioningState Fqdn

articles/azure-functions/functions-dotnet-dependency-injection.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,10 +64,10 @@ namespace MyNamespace
6464
private readonly IMyService _service;
6565
private readonly HttpClient _client;
6666

67-
public HttpTrigger(IMyService service, HttpClient client)
67+
public HttpTrigger(IMyService service, IHttpClientFactory httpClientFactory)
6868
{
6969
_service = service;
70-
_client = client;
70+
_client = httpClientFactory.CreateClient();;
7171
}
7272

7373
[FunctionName("GetPosts")]

articles/azure-functions/functions-reference-node.md

Lines changed: 4 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -461,23 +461,16 @@ There are two ways to install packages on your Function App:
461461

462462
## Environment variables
463463

464-
In Functions, [app settings](functions-app-settings.md), such as service connection strings, are exposed as environment variables during execution. You can access these settings using `process.env`, as shown here in the `GetEnvironmentVariable` function:
464+
In Functions, [app settings](functions-app-settings.md), such as service connection strings, are exposed as environment variables during execution. You can access these settings using `process.env`, as shown here in the second and third calls to `context.log()` where we log the `AzureWebJobsStorage` and `WEBSITE_SITE_NAME` environment variables:
465465

466466
```javascript
467-
module.exports = function (context, myTimer) {
467+
module.exports = async function (context, myTimer) {
468468
var timeStamp = new Date().toISOString();
469469

470470
context.log('Node.js timer trigger function ran!', timeStamp);
471-
context.log(GetEnvironmentVariable("AzureWebJobsStorage"));
472-
context.log(GetEnvironmentVariable("WEBSITE_SITE_NAME"));
473-
474-
context.done();
471+
context.log("AzureWebJobsStorage: " + process.env["AzureWebJobsStorage"]);
472+
context.log("WEBSITE_SITE_NAME: " + process.env["WEBSITE_SITE_NAME"]);
475473
};
476-
477-
function GetEnvironmentVariable(name)
478-
{
479-
return name + ": " + process.env[name];
480-
}
481474
```
482475
483476
[!INCLUDE [Function app settings](../../includes/functions-app-settings.md)]

articles/azure-monitor/log-query/cross-workspace-query.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,19 +11,19 @@ ms.service: log-analytics
1111
ms.workload: na
1212
ms.tgt_pltfrm: na
1313
ms.topic: conceptual
14-
ms.date: 11/15/2018
14+
ms.date: 06/05/2019
1515
ms.author: magoedte
1616
---
1717

1818
# Perform cross-resource log queries in Azure Monitor
1919

20-
Previously with Azure Monitor, you could only analyze data from within the current workspace, and it limited your ability to query across multiple workspaces defined in your subscription. Additionally, you could only search telemetry items collected from your web-based application with Application Insights directly in Application Insights or from Visual Studio. This also made it a challenge to natively analyze operational and application data together.
20+
Previously with Azure Monitor, you could only analyze data from within the current workspace, and it limited your ability to query across multiple workspaces defined in your subscription. Additionally, you could only search telemetry items collected from your web-based application with Application Insights directly in Application Insights or from Visual Studio. This also made it a challenge to natively analyze operational and application data together.
2121

22-
Now you can query not only across multiple Log Analytics workspaces, but also data from a specific Application Insights app in the same resource group, another resource group, or another subscription. This provides you with a system-wide view of your data. You can only perform these types of queries in [Log Analytics](portals.md).
22+
Now you can query not only across multiple Log Analytics workspaces, but also data from a specific Application Insights app in the same resource group, another resource group, or another subscription. This provides you with a system-wide view of your data. You can only perform these types of queries in [Log Analytics](portals.md).
2323

2424
## Cross-resource query limits
2525

26-
* The number of Application Insights resources that you can include in a single query is limited to 100.
26+
* The number of Application Insights resources and Log Analytics workspaces that you can include in a single query is limited to 100.
2727
* Cross-resource query is not supported in View Designer. You can Author a query in Log Analytics and pin it to Azure dashboard and [visualize a log search](../../azure-monitor/learn/tutorial-logs-dashboards.md#visualize-a-log-search).
2828
* Cross-resource query in log alerts is supported in the new [scheduledQueryRules API](https://docs.microsoft.com/rest/api/monitor/scheduledqueryrules). By default, Azure Monitor uses the [legacy Log Analytics Alert API](../platform/api-alerts.md) for creating new log alert rules from Azure portal, unless you switch from [legacy Log Alerts API](../platform/alerts-log-api-switch.md#process-of-switching-from-legacy-log-alerts-api). After the switch, the new API becomes the default for new alert rules in Azure portal and it lets you create cross-resource query log alerts rules. You can create cross-resource query log alert rules without making the switch by using the [ARM template for scheduledQueryRules API](../platform/alerts-log.md#log-alert-with-cross-resource-query-using-azure-resource-template) – but this alert rule is manageable though [scheduledQueryRules API](https://docs.microsoft.com/rest/api/monitor/scheduledqueryrules) and not from Azure portal.
2929

articles/backup/backup-azure-backup-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -177,8 +177,8 @@ Azure Backup storage architecture gives you the best of both worlds by optimally
177177
### Is there a limit on the number of recovery points that can be created?
178178
You can create up to 9999 recovery points per protected instance. A protected instance is a computer, server (physical or virtual), or workload that backs up to Azure.
179179

180-
- Learn more about [backup and retention](./backup-introduction-to-azure-backup.md#backup-and-retention).
181-
- Learn about [protected instances](./backup-introduction-to-azure-backup.md#what-is-a-protected-instance)?
180+
- Learn more about [backup and retention](./backup-overview.md#backup-and-retention).
181+
182182

183183
### How many times can I recovery data that's backed up to Azure?
184184
There is no limit on the number of recoveries from Azure Backup.

articles/backup/backup-azure-manage-windows-server.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ The prerequisites for this article are: an Azure subscription, a Recovery Servic
2424

2525
To monitor alerts, or view management data about a Recovery Services vault, open the vault.
2626

27-
1. Sign in to the [Azure Portal](https://portal.azure.com/) using your Azure subscription.
27+
1. Sign in to the [Azure portal](https://portal.azure.com/) using your Azure subscription.
2828

2929
2. In the portal, click **All services**.
3030

@@ -150,7 +150,7 @@ Choose the alert severity (Critical or Warning) used to generate email. Currentl
150150

151151
## Manage Backup items
152152

153-
A Recovery Services vault holds many types of backup data. For a complete list of backup types, see [Which applications and workloads can be backed up](backup-introduction-to-azure-backup.md#which-azure-backup-components-should-i-use). To manage the various servers, computers, databases, and workloads, click the **Backup Items** tile to view the contents of the vault.
153+
A Recovery Services vault holds many types of backup data. [Learn more](backup-overview.md#what-can-i-back-up) about what you can back up. To manage the various servers, computers, databases, and workloads, click the **Backup Items** tile to view the contents of the vault.
154154

155155
![Backup items tile](./media/backup-azure-manage-windows-server/backup-items.png)
156156

0 commit comments

Comments
 (0)