# Creating Hostgroups based on Hostnames

# Introduction

Configure host-to-groups.map to create groups based on hosts.

Apply the configurations shown in the Open iT server.

# Configuring `host-to-groups.map`

Open host-to-groups.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.
Specify host names with the following syntax:
Mapping Syntax
```
MAP: HostGroupName (GroupType)
Hostname1
Hostname2
```
It is recommended to include the GroupType, although the mapping will work regardless of its inclusion.

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 'Hostname' and 'hostname', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

Each host can belong to multiple groups.
Example
```
MAP: MNL-Group (Location)
mnl*
```
This example maps all hosts starting with mnl in MNL-Group and using the Location as group type.

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.
Save the changes.

The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.

Open host-to-groups.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.
Specify host names with the following syntax:
Mapping Syntax
```
MAP: HostGroupName (GroupType)
Hostname1
Hostname2
```
It is recommended to include the GroupType, although the mapping will work regardless of its inclusion.

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 'Hostname' and 'hostname', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

Each host can belong to multiple groups.
Example
```
MAP: MNL-Group (Location)
mnl*
```
This example maps all hosts starting with mnl in MNL-Group and using the Location as group type.

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.
Save the changes.

The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.

Licpoll2

(115) Hostgroup License Use v3.0

Licenseevents2

(104) License Logfile Events v2.0
(108) Host License Use Licenseevents
(109) Hostgroup License Use Licenseevents

# 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

# Creating Hostgroups based on Hostnames

# Introduction

# Configuring host-to-groups.map

# Next Steps?

# Configuring `host-to-groups.map`