Classification criteria for new CI

[adminreg]

Hello! I have a few Linux SuSE servers and I'm trying to land them in a newly created CI class for SUSE servers only. I have created a new CI Class   "Linux SuSE" in CI Class Manager, which extends from "Linux Server" table. Then, in the CI Classification => UNIX classification, I have created a new CI called Linux SUSE. New CI has the same CI Identifiers as Linux Server. If I set classification criteria to <$name equals "SuSE"> I'm getting error "Active, couldn't classify, now finished". And discovered item does not get classified. What classification criterias should I use for separate Linux SuSE and other Linux systems?

[Dave Ainsworth]

Why do you want to separate them? Would it not be better to classify these as Linux servers (which they are) and let the OS be set to Suse just like what happens OOTB?

Name I assume will be 'Linux' because it looks for Unix OS (e.g. AIX, Solaris etc.) in the uname -a output and if none match, it sets name to be 'Linux' so you won't be able to use this.

So unless there is something specific in the 'uname -a' output for Suse, I don't think you are going to find anything in the OOTB classification that you can use to specifically classify Suse Linux servers differently.

Regards,

Dave

[adminreg]

Hi, David. Thank you for replay. It's just for practice. Instead of Linux SuSE could be another criteria. For example: we have a few departments in the separate networks and be able to collect data to another table by IP-addresses. It's convenient for us. But we have departments which are in the same network as user's host and we have to divide them without scripts. Perhaps there is a way to add an additional CI identifier or we have to use only criteria which there are in the Hardware [cmdb_ci_hardware]?

[supareub]

How do you set another criteria other than name in classifier, which are in output , like os is linux ubuntu, or name starts with 'CET'?