By default all new problems are classified as cause problems. It is possible to manually reclassify certain problems as symptom problems of the cause problem.
For example, power outage may be the actual root cause why some host is unreachable or some service is down. In this case, "host is unreachable" and "service is down" problems must be classified as symptom problems of "power outage" - the cause problem.
The cause-symptom hierarchy supports only two levels. A problem that is already a symptom cannot be assigned "subordinate" symptom problems; any problems assigned as symptoms to a symptom problem will become symptoms of the same cause problem.
Only cause problems are counted in problem totals in maps, dashboard widgets such as Problems by severity or Problem hosts, etc. However, problem ranking does not affect services.
A symptom problem can be linked to only one cause problem. Symptom problems are not automatically resolved, if the cause problem is resolved or closed.
To reclassify a problem as symptom problem, first select it in the list of problems. One or several problems can be selected.
Then go to the cause problem, and in its context menu click on the Mark selected as symptoms option.
After that, the selected problems will be updated by the server to symptom problems of the cause problem. While that happens, their status column will show UPDATING.
Symptom problems are displayed below the cause problem and marked accordingly in Monotoring -> Problems (and the Problems dashboard widget) - with an icon, smaller font and different background.
In collapsed view, only the cause problem is seen; the existence of symptom problems is indicated by the number in the beginning of the line and the icon for expanding the view.
It is also possible to additionally display symptom problems in normal font and in their own line. For that select Show symptoms in the filter settings or the widget configuration.
A symptom problem can be reverted back to a cause problem. To do that, either: