Skip to content

Commit 8d02fb7

Browse files
authored
Merge pull request #89372 from damabe/1570680-Part8
SEOImprovement: User Story 1570680, Part 8
2 parents 049b5f9 + 6e01ee9 commit 8d02fb7

File tree

6 files changed

+11
-9
lines changed

6 files changed

+11
-9
lines changed

articles/cosmos-db/create-graph-java.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.devlang: java
88
ms.topic: quickstart
99
ms.date: 03/26/2019
1010
ms.author: lbosq
11-
ms.custom: seo-java-july2019, seo-java-august2019
11+
ms.custom: seo-java-july2019, seo-java-august2019, seo-java-september2019
1212

1313
---
1414
# Quickstart: Build a graph database with the Java SDK and the Azure Cosmos DB Table API
@@ -105,7 +105,7 @@ Now go back to the Azure portal to get your connection information and copy it i
105105
106106
Copy the first portion of the URI value.
107107
108-
![View and copy an access key in the Azure portal, Keys page](./media/create-graph-java/keys.png)
108+
![View and copy an access key in the Azure portal, Keys page](./media/create-graph-java/copy-access-key-azure-portal.png)
109109
2. Open the src/remote.yaml file and paste the unique ID value over `$name$` in `hosts: [$name$.graphs.azure.com]`.
110110
111111
Line 1 of remote.yaml should now look similar to
@@ -214,15 +214,15 @@ You can now go back to Data Explorer and see the vertices added to the graph, an
214214
215215
12. Now you can connect rakesh, and ashley. Ensure **ashley** is selected in the **Results** list, then select ![Change the target of a vertex in a graph](./media/create-graph-java/edit-pencil-button.png) next to **Targets** on lower right side. You may need to widen your window to see the button.
216216
217-
![Change the target of a vertex in a graph](./media/create-graph-java/azure-cosmosdb-data-explorer-edit-target.png)
217+
![Change the target of a vertex in a graph - Azure CosmosDB](./media/create-graph-java/azure-cosmosdb-data-explorer-edit-target.png)
218218
219219
13. In the **Target** box enter *rakesh*, and in the **Edge label** box enter *knows*, and then select the check box.
220220
221-
![Add a connection between ashley and rakesh in Data Explorer](./media/create-graph-java/azure-cosmosdb-data-explorer-set-target.png)
221+
![Add a connection in Data Explorer - Azure CosmosDB](./media/create-graph-java/azure-cosmosdb-data-explorer-set-target.png)
222222
223223
14. Now select **rakesh** from the results list and see that ashley and rakesh are connected.
224224
225-
![Two vertices connected in Data Explorer](./media/create-graph-java/azure-cosmosdb-graph-explorer.png)
225+
![Two vertices connected in Data Explorer - Azure CosmosDB](./media/create-graph-java/azure-cosmosdb-graph-explorer.png)
226226
227227
That completes the resource creation part of this tutorial. You can continue to add vertexes to your graph, modify the existing vertexes, or change the queries. Now let's review the metrics Azure Cosmos DB provides, and then clean up the resources.
228228

includes/cosmos-db-create-dbaccount-graph.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@
2828

2929
Select **Review+Create**. You can skip the **Network** and **Tags** section.
3030

31-
![The new account blade for Azure Cosmos DB](./media/cosmos-db-create-dbaccount-graph/azure-cosmos-db-create-new-account.png)
31+
![The new account section for Azure Cosmos DB](./media/cosmos-db-create-dbaccount-graph/azure-cosmos-db-create-new-account.png)
3232

3333
4. The account creation takes a few minutes. Wait for the portal to display the **Congratulations! Your Azure Cosmos DB account was created** page.
3434

includes/cosmos-db-delete-resource-group.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,18 +4,19 @@ ms.service: cosmos-db
44
ms.topic: include
55
ms.date: 03/23/2019
66
ms.author: sngun
7+
ms.custom: seo-java-september2019
78
---
89
When you're done with your web app and Azure Cosmos DB account, you can delete the Azure resources you created so you don't incur more charges. To delete the resources:
910

1011
1. In the Azure portal, select **Resource groups** on the far left. If the left menu is collapsed, select ![Expand button](./media/cosmos-db-delete-resource-group/expand.png) to expand it.
1112

1213
2. Select the resource group you created for this quickstart.
1314

14-
![Metrics in the Azure portal](./media/cosmos-db-delete-resource-group/delete-resources-select.png)
15+
![Select the resource group to delete](./media/cosmos-db-delete-resource-group/delete-resources-select.png)
1516

1617
2. In the new window, select **Delete resource group**.
1718

18-
![Metrics in the Azure portal](./media/cosmos-db-delete-resource-group/delete-resources.png)
19+
![Delete the resource group](./media/cosmos-db-delete-resource-group/delete-resources.png)
1920

2021
3. In the next window, enter the name of the resource group to delete, and then select **Delete**.
2122

includes/cosmos-db-tutorial-review-slas.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ ms.service: cosmos-db
44
ms.topic: include
55
ms.date: 03/22/2019
66
ms.author: sngun
7+
ms.custom: seo-java-september2019
78
---
89
The Azure portal monitors your Cosmos DB account throughput, storage, availability, latency, and consistency. Charts for metrics associated with an [Azure Cosmos DB Service Level Agreement (SLA)](https://azure.microsoft.com/support/legal/sla/cosmos-db/) show the SLA value compared to actual performance. This suite of metrics makes monitoring your SLAs transparent.
910

@@ -13,7 +14,7 @@ To review metrics and SLAs:
1314

1415
2. Select a tab such as **Latency**, and select a timeframe on the right. Compare the **Actual** and **SLA** lines on the charts.
1516

16-
![Azure Cosmos DB metrics suite](./media/cosmos-db-tutorial-review-slas/metrics-suite.png)
17+
![Azure Cosmos DB metrics suite](./media/cosmos-db-tutorial-review-slas/azure-cosmosdb-metrics-suite.png)
1718

1819
3. Review the metrics on the other tabs.
1920

0 commit comments

Comments
 (0)