Skip to content

Commit a869f4c

Browse files
committed
Remove references to include
1 parent 335f34c commit a869f4c

6 files changed

+0
-11
lines changed

articles/log-analytics/log-analytics-app-insights-connector.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,6 @@ Click the **Application Insights** tile to open the **Application Insights** das
8484

8585
The dashboard includes the blades shown in the table. Each blade lists up to 10 items matching that blade's criteria for the specified scope and time range. You can run a log search that returns all records when you click **See all** at the bottom of the blade or when you click the blade header.
8686

87-
[!INCLUDE [log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
8887

8988
| **Column** | **Description** |
9089
| --- | --- |

articles/log-analytics/log-analytics-scom-assessment.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -225,8 +225,6 @@ View the summarized compliance assessments for your infrastructure and then dril
225225

226226
If you have recommendations that you want to ignore, you can create a text file that Log Analytics uses to prevent recommendations from appearing in your assessment results.
227227

228-
[!INCLUDE[log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
229-
230228
### To identify recommendations that you want to ignore
231229
1. In the Azure portal on the Log Analytics workspace page for your selected workspace, click the **Log Search** menu item.
232230
2. Use the following query to list recommendations that have failed for computers in your environment.

articles/log-analytics/log-analytics-service-fabric-azure-resource-manager.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77,8 +77,6 @@ Following the same steps above, input the necessary parameters, and kick off a d
7777
To view Perf Data from your nodes:
7878

7979

80-
[!INCLUDE [log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
81-
8280
- Launch the Log Analytics workspace from the Azure portal.
8381
![Service Fabric](./media/log-analytics-service-fabric/6.png)
8482
- Go to Settings on the left pane, and select Data >> Windows Performance Counters >> "Add the selected performance counters":

articles/log-analytics/log-analytics-sql-assessment.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -170,8 +170,6 @@ View the summarized compliance assessments for your infrastructure and then dril
170170
## Ignore recommendations
171171
If you have recommendations that you want to ignore, you can create a text file that Log Analytics will use to prevent recommendations from appearing in your assessment results.
172172

173-
[!INCLUDE[log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
174-
175173
### To identify recommendations that you will ignore
176174
1. In the Azure portal on the Log Analytics workspace page for your selected workspace, click the **Log Search** tile.
177175
2. Use the following query to list recommendations that have failed for computers in your environment.

articles/log-analytics/log-analytics-vmware.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -149,8 +149,6 @@ If you want to see additional ESXi host VM creation data, click an ESXi host nam
149149
#### Common search queries
150150
The solution includes other useful queries that can help you manage your ESXi hosts, such as high storage space, storage latency, and path failure.
151151
152-
[!INCLUDE[log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
153-
154152
![queries](./media/log-analytics-vmware/queries.png)
155153
156154

articles/log-analytics/log-analytics-wire-data.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -383,8 +383,6 @@ In the **Overview** page for your Log Analytics workspace in the Azure portal, c
383383
| Local Subnets | Shows the number of local subnets that agents have discovered. Click the number to run a log search for <code>Type:WireData &#124; Measure Sum(TotalBytes) by LocalSubnet</code> that lists all subnets with the number of bytes sent over each one. Click a subnet in the list to run a log search returning the total number of bytes sent over the subnet. |
384384
| Application-level Protocols | Shows the number of application-level protocols in use, as discovered by agents. Click the number to run a log search for <code>Type:WireData &#124; Measure Sum(TotalBytes) by ApplicationProtocol</code>. Click a protocol to run a log search returning the total number of bytes sent using the protocol. |
385385

386-
[!INCLUDE[log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
387-
388386
![Wire Data dashboard](./media/log-analytics-wire-data/wire-data-dash.png)
389387

390388
You can use the **Agents capturing network traffic** blade to determine how much network bandwidth is being consumed by computers. This blade can help you easily find the _chattiest_ computer in your environment. Such computers could be overloaded, acting abnormally, or using more network resources than normal.

0 commit comments

Comments
 (0)