# Mapping User IP Address to Hostname

# Introduction

Configure ip-to-hostname.map to map user IP addresses to hostnames.

# Configuring ip-to-hostname.map

  1. Open ip-to-hostname.map in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration.

    Notice that it contains instructions on how to edit the file.

  2. Specify IP addresses with the following syntax:

    Mapping Syntax
    MAP: host_name    
    <IP_address1>      
    <IP_address2>  

    Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimize Rules to Speed-up Rename or Mapping page.

    In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Host' and 'host', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

    Example
    MAP: MNLHost01   
    10.124.113.250
    10.56.43.78
    10.214.139.109

    This example maps 10.124.113.250, 10.56.43.78 and 10.214.139.109 to MNLHost01 hostname.

    You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.

  3. Save the changes.

  1. Open ip-to-hostname.map in the etc directory, which is by default in /var/opt/openit/etc.

    Notice that it contains instructions on how to edit the file.

  2. Specify IP addresses with the following syntax:

    Mapping Syntax
    MAP: host_name     
    <IP_address1>      
    <IP_address2>  

    Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimize Rules to Speed-up Rename or Mapping page.

    In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Host' and 'host', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

    Example
    MAP: MNLHost01    
    10.124.113.250
    10.56.43.78
    10.214.139.109

    This example maps 10.124.113.250, 10.56.43.78 and 10.214.139.109 to MNLHost01 hostname.

    You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.

  3. Save the changes.

Webappbrowseractivity

Webappproxylog

# Next Steps?

Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the real-time and historical reports.

For real-time reports:

   Generating License Status Data  

For historical reports:

   Data Generation  

We value your feedback!

Please take a few minutes to complete our survey and share your thoughts on your recent experience with our documentation.

Take survey

Close