You see no syslog events on event console in OneClick for one SpectroSERVER.
Each environment handles syslog differently. Here we see:
The sysedge model representing the secondary SS sending the syslogs did not exist for the problematic landscape. All other landscapes were represented with a sysedge model and showed alarms.
We modelled manually a new sysedge model to represent the secondary SpectroSERVER.
There are no logs with rsyslog to verify what traps are processed so a TCPdump will be helpful here.
AlertManager debug is also useful and showed the problem here.