Interface services don’t have very descriptive names by default in Check_MK. Out of the box, these services are named “Interface #” as they’re discovered, with an integer in place of the #.
![](https://truepath.wpengine.com/wp-content/uploads/2019/09/01_theproblem.png)
This is great from one perspective, and frustrating from a dozen others.
To alter this behavior, open your Rulesets in WATO
![](https://truepath.wpengine.com/wp-content/uploads/2019/09/02_wato_rulesets.png)
Seach for alias and open the ruleset Network Interface and Switch Port Discovery
![](https://truepath.wpengine.com/wp-content/uploads/2019/09/03_searchrules-1.png)
![](https://truepath.wpengine.com/wp-content/uploads/2019/09/04_choosediscovery-1024x272.png)
Choose the appropriate folder and click Create Rule in Folder
![](https://truepath.wpengine.com/wp-content/uploads/2019/09/05_newrule.png)
Give your rule an appropriate name, and in the Value section, check the box beside Alias as service name for network interface checks. Ensure Use Alias is chosen below it.
![](https://truepath.wpengine.com/wp-content/uploads/2019/09/06_rulespec.png)
Once you Save the new rule, you’ll need to Commit the changes.
![](https://truepath.wpengine.com/wp-content/uploads/2019/09/07_activate.png)
Don’t forget to Bulk Discover your hosts!
![](https://truepath.wpengine.com/wp-content/uploads/2019/09/08_discover-1024x196.png)
The result? Great interface service names!
![](https://truepath.wpengine.com/wp-content/uploads/2019/09/09_results.png)