Hi,
I have a problem with SLA propagation. Steps taken:
1. created a custom key (based on file checksum)
2. created a simple trigger (fires off when file checksum changes, disaster level)
3. created a service linked with my trigger, no algorithm, not showing SLA
4. created a higher level service, show SLA, MIN algorithm
5. linked pt. 3. as a child to pt. 4
Now when I fire off my trigger, service form pt. 3 changes ststus to disaster, the status propagates to service from pt. 4, but time still is counted for the 'OK' time, not for the 'Problem' time.
Server log says:
I'm using the 1.4
I have a problem with SLA propagation. Steps taken:
1. created a custom key (based on file checksum)
2. created a simple trigger (fires off when file checksum changes, disaster level)
3. created a service linked with my trigger, no algorithm, not showing SLA
4. created a higher level service, show SLA, MIN algorithm
5. linked pt. 3. as a child to pt. 4
Now when I fire off my trigger, service form pt. 3 changes ststus to disaster, the status propagates to service from pt. 4, but time still is counted for the 'OK' time, not for the 'Problem' time.
Server log says:
Code:
15183:20070605:104210 Query failed: [insert into service_alarms(serviceid,clock,value) values(10,1181032930,5)] Duplicate entry '0' for key 1 [1062]
Comment