IIS Log Configuration

Ship logs from your IIS Websites to Logstash

Configure Filebeat to ship logs from IIS applications to Logstash and Elasticsearch.

Step 1 - Install Filebeat

deb (Debian/Ubuntu/Mint)

curl -L -O https://artifacts.elastic.co/downloads/beats//-oss-7.15.1-amd64.deb
sudo dpkg -i -oss-7.15.1-amd64.deb

rpm (CentOS/RHEL/Fedora)

curl -L -O https://artifacts.elastic.co/downloads/beats//-oss-7.15.1-x86_64.rpm
sudo rpm -vi -oss-7.15.1-x86_64.rpm

macOS

curl -L -O https://artifacts.elastic.co/downloads/beats//-oss-7.15.1-darwin-x86_64.tar.gz
tar xzvf -oss-7.15.1-darwin-x86_64.tar.gz

Windows

Download and extract the Windows zip file.
Rename the -<version>-windows directory to ``.
Open a PowerShell prompt as an Administrator.
Run the following to install as a Windows service:

.\install-service-.ps1

If script execution is disabled on your system, you need to set the execution policy for the current session to allow the script to run. For example: PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-.ps1.

My OS isn't here! Chat to support now

Step 2 - Enable IIS module in Filebeat

We need to enable the IIS module in Filebeat so that filebeat know to look for IIS logs. In Powershell run the following command:

.\Filebeat modules enable iis

Additional module configuration can be done using the per module config files located in the modules.d folder, most commonly this would be to read logs from a non-default location

win <EXTRACTED_ARCHIVE>/modules.d/

- module: iis
# Access logs
access:
  enabled: true

  # Set custom paths for the log files. If left empty,
  # Filebeat will choose the paths depending on your OS.
  var.paths: ["/custom/path/to/logs"]

# Error logs
error:
  enabled: true

  # Set custom paths for the log files. If left empty,
  # Filebeat will choose the paths depending on your OS.
  var.paths: ["/custom/path/to/logs"]

Step 3 - Copy configuration File

The configuration file below is pre-configured to send data to your Logit.io Stack via Logstash.

Copy the configuration file below and overwrite the contents of filebeat.yml.

# ============================== Filebeat modules ==============================

filebeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: false

  # Period on which files under path should be checked for changes
  #reload.period: 10s

# ======================= Elasticsearch template setting =======================

setup.template.settings:
  index.number_of_shards: 1
  #index.codec: best_compression
  #_source.enabled: false

# ================================== Outputs ===================================
# ------------------------------ Logstash Output -------------------------------
<div class="sw-warning">
    <b>No input available! </b> Your stack is missing the required input for this data source <a href="#" onclick="Intercom('showNewMessage')" class="btn btn-info btn-sm">Talk to support to add the input</a>
</div>

Step 4 - Start Filebeat

Now we need to start the Filebeat service. In powershell run the following command:

Start-Service filebeat

Step 5 - how to diagnose no data in Stack

If you don't see data appearing in your Stack after following the steps, visit the Help Centre guide for steps to diagnose no data appearing in your Stack or Chat to support now.

Step 6 - IIS dashboard

The IIS module comes with predefined Kibana dashboards. To view your dashboards for any of your Logit.io stacks, launch Kibana and choose Dashboards.

Predefined kibana dashboard screenshot

Step 7 - IIS Logging Overview

Applications developed for .NET can be hosted on an IIS (Internet Information Services) web server which can only be used on the Windows operating system. IIS is commonly used to host web apps & static sites running on ASP.Net.

IIS is known for its high flexibility & rich features. The most recent version of IIS includes a number of out of the box security features including request filters, client certificate mapping & URL authorisation.

Modules for the latest version of IIS can be added as extensions to your configuration if required to process requests. These include modules for security, compression, content & caching which all hold a wealth of unique features essential to server administration teams.

Remote management is also included as part of the server’s functionality making it an ideal choice for DevOps teams undertaking remote work.

All of this server activity generates a huge amount of log data for analysis. Our IIS log file analyser can be used to centralise your data & set up alerts to monitor your application security in real-time as well as deliver metrics for Kibana visualisations & reports easily.

If you need any further assistance with analysing your IIS logs we're here to help you get started. Feel free to reach out by contacting our support team by visiting our dedicate Help Centre or via live chat & we'll be happy to assist.

Expand View