Skip to content

Commit 8770014

Browse files
authored
Update iis-7.md
1 parent 87a12b3 commit 8770014

File tree

1 file changed

+2
-9
lines changed
  • docs/integrations/microsoft-azure

1 file changed

+2
-9
lines changed

docs/integrations/microsoft-azure/iis-7.md

Lines changed: 2 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,6 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
1111

1212
The IIS 7 App monitors the performance and reliability of your Microsoft Internet Information Services (IIS) infrastructure, identifying customer-facing and internal operational issues. Additionally, you can monitor customer paths and interactions to learn how customers are using your product. The app consists of predefined searches and Dashboards, which provide visibility into your environment for real-time or historical analysis.
1313

14-
1514
## Log types
1615

1716
IIS 7 Logs (IIS 7.5 logs are used) are generated as local files and written to this directory by default: `C:\inetpub\Logs\LogFiles\W3SVC1`. The App assumes the following format:
@@ -66,7 +65,6 @@ _sourceCategory=IIS*
6665
| transpose row _timeslice column app
6766
```
6867

69-
7068
The following query is taken from the **OSes and Browsers** panel of the **IIS 7 Traffic Insights - Content and Client Platform Dashboard**.
7169

7270
```sql title="Operating Systems (OSes) and Browsers"
@@ -93,12 +91,10 @@ if (agent matches "Dolphin*","Dolphin", Browser) as Browser
9391
| transpose row os column browser as *
9492
```
9593

96-
9794
## Collecting logs for IIS 7
9895

9996
This procedure explains how to enable logging from Microsoft Internet Information Services (IIS) on your Windows server and ingest the logs into Sumo Logic.
10097

101-
10298
### Prerequisites
10399

104100
To prepare for logging IIS 7 events, perform the following two tasks.
@@ -137,12 +133,10 @@ To confirm that the log files are being created, do the following:
137133
1. Open a command-line window and change directories to `C:\inetpub\Logs\LogFiles`. This is the same path you will enter when you configure the Source to collect these files.
138134
2. Under the `\W3SVC1` directory, you should see one or more files with a `.log` extension. If the file is present, you can collect it.
139135

140-
141136
### Step 1: Configure a Collector
142137

143138
Configure an [Installed Collector (Windows)](/docs/send-data/installed-collectors/windows). Sumo Logic recommends that you install the collector on the same system that hosts the logs.
144139

145-
146140
### Step 2: Configure a Source
147141

148142
To collect logs from IIS 7, use an Installed Collector and a Local File Source. You may also configure a [Remote File Source](/docs/send-data/installed-collectors/sources/remote-file-source), but the configuration is more complex. Sumo Logic recommends using a Local File Source if possible.
@@ -166,14 +160,13 @@ To collect logs from IIS 7, use an Installed Collector and a Local File Source.
166160

167161
After a few minutes, your new Source should be propagated down to the Collector and will begin submitting your IIS log files to the Sumo Logic service.
168162

169-
170163
## Field Extraction Rules
171164

172165
<br/>
173166
**FER to normalize the fields**. Field Extraction Rule named **AppObservabilityIIS7FER** is automatically created for IIS 7/8 Application Components.
174167
<br/>
175168

176-
## Installing the IIS 7 App
169+
## Installing the IIS 7 app
177170

178171
import AppInstall from '../../reuse/apps/app-install-v2.md';
179172

@@ -193,7 +186,7 @@ As part of the app installation process, the following fields will be created by
193186
* `cs_uri_stem`
194187
* `cs_username`
195188

196-
## Viewing IIS 7 Dashboards
189+
## Viewing IIS 7 dashboards
197190

198191
import ViewDashboards from '../../reuse/apps/view-dashboards.md';
199192

0 commit comments

Comments
 (0)