-
Notifications
You must be signed in to change notification settings - Fork 2
/
Template SPLM Server General.xml
1519 lines (1519 loc) · 77.6 KB
/
Template SPLM Server General.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<zabbix_export>
<version>5.0</version>
<date>2021-08-16T20:19:35Z</date>
<groups>
<group>
<name>Teamcenter Server Components</name>
</group>
</groups>
<templates>
<template>
<template>Template SPLM Server General</template>
<name>Template SPLM Server General</name>
<templates>
<template>
<name>Template Module Windows network by Zabbix agent active</name>
</template>
</templates>
<groups>
<group>
<name>Teamcenter Server Components</name>
</group>
</groups>
<applications>
<application>
<name>Business Logic (Teamcenter)</name>
</application>
<application>
<name>CPU</name>
</application>
<application>
<name>Filesystems</name>
</application>
<application>
<name>General</name>
</application>
<application>
<name>Inventory</name>
</application>
<application>
<name>Memory</name>
</application>
<application>
<name>Monitoring agent</name>
</application>
<application>
<name>Services</name>
</application>
<application>
<name>Status</name>
</application>
<application>
<name>Storage</name>
</application>
<application>
<name>Storage Information</name>
</application>
<application>
<name>Top 5 Processes</name>
</application>
</applications>
<items>
<item>
<name>Host name of Zabbix agent running</name>
<type>ZABBIX_ACTIVE</type>
<key>agent.hostname</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>0</trends>
<status>DISABLED</status>
<value_type>CHAR</value_type>
<applications>
<application>
<name>Monitoring agent</name>
</application>
</applications>
<preprocessing>
<step>
<type>DISCARD_UNCHANGED_HEARTBEAT</type>
<params>1d</params>
</step>
</preprocessing>
</item>
<item>
<name>Zabbix agent ping</name>
<type>ZABBIX_ACTIVE</type>
<key>agent.ping</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<description>The agent always returns 1 for this item. It could be used in combination with nodata() for availability check.</description>
<applications>
<application>
<name>Status</name>
</application>
</applications>
<valuemap>
<name>Zabbix agent ping status</name>
</valuemap>
<triggers>
<trigger>
<expression>{nodata({$AGENT.NODATA_TIMEOUT})}=1</expression>
<name>Zabbix agent is not available (or nodata for {$AGENT.NODATA_TIMEOUT})</name>
<priority>AVERAGE</priority>
<description>For active agents, nodata() with agent.ping is used with {$AGENT.NODATA_TIMEOUT} as time threshold.</description>
<manual_close>YES</manual_close>
</trigger>
</triggers>
</item>
<item>
<name>Version of Zabbix agent running</name>
<type>ZABBIX_ACTIVE</type>
<key>agent.version</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>0</trends>
<status>DISABLED</status>
<value_type>CHAR</value_type>
<applications>
<application>
<name>Monitoring agent</name>
</application>
</applications>
<preprocessing>
<step>
<type>DISCARD_UNCHANGED_HEARTBEAT</type>
<params>1d</params>
</step>
</preprocessing>
</item>
<item>
<name>Disk Space Forecaset 1 Hour</name>
<type>CALCULATED</type>
<key>forecast.disk.1h</key>
<delay>5s</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>B</units>
<params>forecast("vfs.fs.size[C:,free]",60m,,60m)</params>
<applications>
<application>
<name>Storage Information</name>
</application>
</applications>
</item>
<item>
<name>Disk Space Forecaset 3 Day</name>
<type>CALCULATED</type>
<key>forecast.disk.3d</key>
<delay>5s</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>B</units>
<params>forecast("vfs.fs.size[C:,free]",3d,,3d)</params>
<applications>
<application>
<name>Storage Information</name>
</application>
</applications>
</item>
<item>
<name>Disk Space Forecaset 4 Hour</name>
<type>CALCULATED</type>
<key>forecast.disk.4h</key>
<delay>5s</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>B</units>
<params>forecast("vfs.fs.size[C:,free]",240m,,240m)</params>
<applications>
<application>
<name>Storage Information</name>
</application>
</applications>
</item>
<item>
<name>Disk Space Forecaset 8 Hour</name>
<type>CALCULATED</type>
<key>forecast.disk.8h</key>
<delay>5s</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>B</units>
<params>forecast("vfs.fs.size[C:,free]",480m,,480m)</params>
<applications>
<application>
<name>Storage Information</name>
</application>
</applications>
</item>
<item>
<name>Volume Forecaset 1 Hour</name>
<type>CALCULATED</type>
<key>forecast.vol.1h</key>
<delay>5s</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>B</units>
<params>forecast("vfs.dir.size[c:\siemens\vol_sys]",60m,,60m)</params>
<applications>
<application>
<name>Storage Information</name>
</application>
</applications>
</item>
<item>
<name>Volume Forecaset 4 Hour</name>
<type>CALCULATED</type>
<key>forecast.vol.4h</key>
<delay>5s</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>B</units>
<params>forecast("vfs.dir.size[c:\siemens\vol_sys]",240m,,240m)</params>
<applications>
<application>
<name>Storage Information</name>
</application>
</applications>
</item>
<item>
<name>The High Load Process, more than {$PROCESS.ALARM}</name>
<key>HighLoadProcess[{$PROCESS.ALARM}]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>0</trends>
<value_type>CHAR</value_type>
<applications>
<application>
<name>CPU</name>
</application>
</applications>
<preprocessing>
<step>
<type>TRIM</type>
<params>name ---- </params>
</step>
</preprocessing>
</item>
<item>
<name>Is The Server Available?</name>
<type>SIMPLE</type>
<key>icmpping[,4]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<applications>
<application>
<name>Status</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{last(4m)}=0</expression>
<name>The server {HOST.NAME} is not available!</name>
<priority>DISASTER</priority>
<description>You should checking the networks, networks interfaces and so on.</description>
<manual_close>YES</manual_close>
</trigger>
</triggers>
</item>
<item>
<name>Number of mention about "Explain Plan" in logs</name>
<type>ZABBIX_ACTIVE</type>
<key>logrt.count["C:\\TCLOGS\\tcserver\.([a-zA-Z0-9])+.syslog","(Explain Plan)",,,all,,]</key>
<delay>1s</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<applications>
<application>
<name>Business Logic (Teamcenter)</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{last(1m)}<>0</expression>
<name>Teamcenter Alert: Business Logic Server has a problem DBMS performance</name>
<url>http://dba-oracle.com/googlesearchsite_proc.htm?cx=000522505899594707971%3A4-ldikxixw4&cof=FORID%3A10&ie=UTF-8&q=Slow+Oracle+SQL&sa=Search&siteurl=www.dba-oracle.com%2Ft_find_slow_oracle_sql.htm&ref=www.google.com%2F&ss=3229j10291705j3</url>
<priority>HIGH</priority>
<description>1.Check your Teamcenter syslog and the seeking the strings that contained "Explain Plan"
2.Check your Database</description>
<manual_close>YES</manual_close>
</trigger>
</triggers>
</item>
<item>
<name>Number of failed connection TC-DBMS</name>
<type>ZABBIX_ACTIVE</type>
<key>logrt.count["C:\\TCLOGS\\tcserver\.([a-zA-Z0-9])+.syslog","(the DBMS is not online)",,,all,,]</key>
<delay>1s</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<applications>
<application>
<name>Business Logic (Teamcenter)</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{last(1m)}<>0</expression>
<recovery_mode>NONE</recovery_mode>
<name>Teamcenter Alert: Business Logic Server can not connect to DBMS</name>
<url>https://support.sw.siemens.com/en-US/product/282219420/knowledge-base/PL8009139?pid=sc%3Asearch&pid_context=install%20-ayt&index=content-external&audience=external</url>
<priority>DISASTER</priority>
<description>Teamcenter business logic cannot connect to DBMS.
1.Check your Teamcenter syslog.
2.Check your Database and passwod life of infodba user.</description>
<manual_close>YES</manual_close>
</trigger>
</triggers>
</item>
<item>
<name>Cache bytes</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\Memory\Cache Bytes"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<units>B</units>
<description>Cache Bytes is the sum of the Memory\\System Cache Resident Bytes, Memory\\System Driver Resident Bytes,
Memory\\System Code Resident Bytes, and Memory\\Pool Paged Resident Bytes counters. This counter displays
the last observed value only; it is not an average.</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
</item>
<item>
<name>Free system page table entries</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\Memory\Free System Page Table Entries"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<description>This indicates the number of page table entries not currently in use by the system. If the number is less
than 5,000, there may well be a memory leak or you running out of memory.</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{max(5m)}<{$MEM.PAGE_TABLE_CRIT.MIN}</expression>
<name>Number of free system page table entries is too low (less {$MEM.PAGE_TABLE_CRIT.MIN} for 5m)</name>
<priority>WARNING</priority>
<description>The Memory Free System Page Table Entries is less than {$MEM.PAGE_TABLE_CRIT.MIN} for 5 minutes. If the number is less than 5,000, there may well be a memory leak.</description>
<dependencies>
<dependency>
<name>High memory utilization ( >{$MEMORY.UTIL.MAX}% for 5m)</name>
<expression>{Template SPLM Server General:vm.memory.util.min(5m)}>{$MEMORY.UTIL.MAX}</expression>
</dependency>
</dependencies>
</trigger>
</triggers>
</item>
<item>
<name>Memory page faults per second</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\Memory\Page Faults/sec"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<value_type>FLOAT</value_type>
<description>Page Faults/sec is the average number of pages faulted per second. It is measured in number of pages
faulted per second because only one page is faulted in each fault operation, hence this is also equal
to the number of page fault operations. This counter includes both hard faults (those that require
disk access) and soft faults (where the faulted page is found elsewhere in physical memory.) Most
processors can handle large numbers of soft faults without significant consequence. However, hard faults,
which require disk access, can cause significant delays.</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
</item>
<item>
<name>Memory pages per second</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\Memory\Pages/sec"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<value_type>FLOAT</value_type>
<description>This measures the rate at which pages are read from or written to disk to resolve hard page faults.
If the value is greater than 1,000, as a result of excessive paging, there may be a memory leak.</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{min(5m)}>{$MEM.PAGE_SEC.CRIT.MAX}</expression>
<name>The Memory Pages/sec is too high (over {$MEM.PAGE_SEC.CRIT.MAX} for 5m)</name>
<priority>WARNING</priority>
<description>The Memory Pages/sec in the last 5 minutes exceeds {$MEM.PAGE_SEC.CRIT.MAX}. If the value is greater than 1,000, as a result of excessive paging, there may be a memory leak.</description>
<dependencies>
<dependency>
<name>High memory utilization ( >{$MEMORY.UTIL.MAX}% for 5m)</name>
<expression>{Template SPLM Server General:vm.memory.util.min(5m)}>{$MEMORY.UTIL.MAX}</expression>
</dependency>
</dependencies>
</trigger>
</triggers>
</item>
<item>
<name>Memory pool non-paged</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\Memory\Pool Nonpaged Bytes"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<units>B</units>
<description>This measures the size, in bytes, of the non-paged pool. This is an area of system memory for objects
that cannot be written to disk but instead must remain in physical memory as long as they are allocated.
There is a possible memory leak if the value is greater than 175MB (or 100MB with the /3GB switch).
A typical Event ID 2019 is recorded in the system event log.</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
</item>
<item>
<name>CPU DPC time</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\Processor Information(_total)\% DPC Time"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<value_type>FLOAT</value_type>
<units>%</units>
<description>Processor DPC time is the time that a single processor spent receiving and servicing deferred procedure
calls (DPCs). DPCs are interrupts that run at a lower priority than standard interrupts. % DPC Time is a
component of % Privileged Time because DPCs are executed in privileged mode. If a high % DPC Time is
sustained, there may be a processor bottleneck or an application or hardware related issue that can
significantly diminish overall system performance.</description>
<applications>
<application>
<name>CPU</name>
</application>
</applications>
</item>
<item>
<name>CPU interrupt time</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\Processor Information(_total)\% Interrupt Time"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<value_type>FLOAT</value_type>
<units>%</units>
<description>The Processor Information\% Interrupt Time is the time the processor spends receiving and servicing
hardware interrupts during sample intervals. This value is an indirect indicator of the activity of
devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication
lines, network interface cards and other peripheral devices. This is an easy way to identify a potential
hardware failure. This should never be higher than 20%.</description>
<applications>
<application>
<name>CPU</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{min(5m)}>{$CPU.INTERRUPT.CRIT.MAX}</expression>
<name>CPU interrupt time is too high (over {$CPU.INTERRUPT.CRIT.MAX}% for 5m)</name>
<priority>WARNING</priority>
<description>"The CPU Interrupt Time in the last 5 minutes exceeds {$CPU.INTERRUPT.CRIT.MAX}%."
The Processor Information\% Interrupt Time is the time the processor spends receiving and servicing
hardware interrupts during sample intervals. This value is an indirect indicator of the activity of
devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication
lines, network interface cards and other peripheral devices. This is an easy way to identify a potential
hardware failure. This should never be higher than 20%.</description>
<dependencies>
<dependency>
<name>High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)</name>
<expression>{Template SPLM Server General:system.cpu.util[].min(5m)}>{$CPU.UTIL.CRIT}</expression>
</dependency>
</dependencies>
</trigger>
</triggers>
</item>
<item>
<name>CPU privileged time</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\Processor Information(_total)\% Privileged Time"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<value_type>FLOAT</value_type>
<units>%</units>
<description>The Processor Information\% Privileged Time counter shows the percent of time that the processor is spent
executing in Kernel (or Privileged) mode. Privileged mode includes services interrupts inside Interrupt
Service Routines (ISRs), executing Deferred Procedure Calls (DPCs), Device Driver calls and other kernel-mode
functions of the Windows® Operating System.</description>
<applications>
<application>
<name>CPU</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{min(5m)}>{$CPU.PRIV.CRIT.MAX}</expression>
<name>CPU privileged time is too high (over {$CPU.PRIV.CRIT.MAX}% for 5m)</name>
<priority>WARNING</priority>
<description>The CPU privileged time in the last 5 minutes exceeds {$CPU.PRIV.CRIT.MAX}%.</description>
<dependencies>
<dependency>
<name>CPU interrupt time is too high (over {$CPU.INTERRUPT.CRIT.MAX}% for 5m)</name>
<expression>{Template SPLM Server General:perf_counter_en["\Processor Information(_total)\% Interrupt Time"].min(5m)}>{$CPU.INTERRUPT.CRIT.MAX}</expression>
</dependency>
<dependency>
<name>High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)</name>
<expression>{Template SPLM Server General:system.cpu.util[].min(5m)}>{$CPU.UTIL.CRIT}</expression>
</dependency>
</dependencies>
</trigger>
</triggers>
</item>
<item>
<name>CPU user time</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\Processor Information(_total)\% User Time"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>%</units>
<description>The Processor Information\% User Time counter shows the percent of time that the processor(s) is spent executing
in User mode.</description>
<applications>
<application>
<name>CPU</name>
</application>
</applications>
</item>
<item>
<name>Context switches per second</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\System\Context Switches/sec"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<value_type>FLOAT</value_type>
<description>Context Switches/sec is the combined rate at which all processors on the computer are switched from one thread to another.
Context switches occur when a running thread voluntarily relinquishes the processor, is preempted by a higher priority ready thread, or switches between user-mode and privileged (kernel) mode to use an Executive or subsystem service.
It is the sum of Thread\\Context Switches/sec for all threads running on all processors in the computer and is measured in numbers of switches.
There are context switch counters on the System and Thread objects. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.</description>
<applications>
<application>
<name>CPU</name>
</application>
</applications>
</item>
<item>
<name>CPU queue length</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\System\Processor Queue Length"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<value_type>FLOAT</value_type>
<description>The Processor Queue Length shows the number of threads that are observed as delayed in the processor Ready Queue
and are waiting to be executed.</description>
<applications>
<application>
<name>CPU</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{min(5m)}>{$CPU.QUEUE.CRIT.MAX}</expression>
<name>CPU queue length is too high (over {$CPU.QUEUE.CRIT.MAX} for 5m)</name>
<priority>WARNING</priority>
<description>The CPU Queue Length in the last 5 minutes exceeds {$CPU.QUEUE.CRIT.MAX}.</description>
<dependencies>
<dependency>
<name>High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)</name>
<expression>{Template SPLM Server General:system.cpu.util[].min(5m)}>{$CPU.UTIL.CRIT}</expression>
</dependency>
</dependencies>
</trigger>
</triggers>
</item>
<item>
<name>Number of threads</name>
<type>ZABBIX_ACTIVE</type>
<key>perf_counter_en["\System\Threads"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<description>The number of threads used by all running processes.</description>
<applications>
<application>
<name>General</name>
</application>
</applications>
</item>
<item>
<name>Number of processes</name>
<type>ZABBIX_ACTIVE</type>
<key>proc.num[]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<description>The number of processes.</description>
<applications>
<application>
<name>General</name>
</application>
</applications>
</item>
<item>
<name>CPU utilization</name>
<type>ZABBIX_ACTIVE</type>
<key>system.cpu.util[]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>%</units>
<description>CPU utilization in %</description>
<applications>
<application>
<name>CPU</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{min(5m)}>{$CPU.UTIL.CRIT}</expression>
<name>High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)</name>
<opdata>Current utilization: {ITEM.LASTVALUE1}</opdata>
<priority>WARNING</priority>
<description>CPU utilization is too high. The system might be slow to respond.</description>
</trigger>
</triggers>
</item>
<item>
<name>System name</name>
<type>ZABBIX_ACTIVE</type>
<key>system.hostname</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>0</trends>
<status>DISABLED</status>
<value_type>CHAR</value_type>
<description>System host name.</description>
<inventory_link>NAME</inventory_link>
<applications>
<application>
<name>General</name>
</application>
</applications>
<preprocessing>
<step>
<type>DISCARD_UNCHANGED_HEARTBEAT</type>
<params>1d</params>
</step>
</preprocessing>
<triggers>
<trigger>
<expression>{diff()}=1 and {strlen()}>0</expression>
<name>System name has changed (new name: {ITEM.VALUE})</name>
<priority>INFO</priority>
<description>System name has changed. Ack to close.</description>
<manual_close>YES</manual_close>
</trigger>
</triggers>
</item>
<item>
<name>System local time</name>
<key>system.localtime</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<units>unixtime</units>
<description>System local time of the host.</description>
<applications>
<application>
<name>General</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{fuzzytime({$SYSTEM.FUZZYTIME.MAX})}=0</expression>
<name>System time is out of sync (diff with Zabbix server > {$SYSTEM.FUZZYTIME.MAX}s)</name>
<priority>WARNING</priority>
<description>The host system time is different from the Zabbix server time.</description>
<manual_close>YES</manual_close>
</trigger>
</triggers>
</item>
<item>
<name>Operating system architecture</name>
<type>ZABBIX_ACTIVE</type>
<key>system.sw.arch</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>0</trends>
<status>DISABLED</status>
<value_type>CHAR</value_type>
<description>Operating system architecture of the host.</description>
<applications>
<application>
<name>Inventory</name>
</application>
</applications>
<preprocessing>
<step>
<type>DISCARD_UNCHANGED_HEARTBEAT</type>
<params>1d</params>
</step>
</preprocessing>
</item>
<item>
<name>Free swap space</name>
<type>ZABBIX_ACTIVE</type>
<key>system.swap.size[,free]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<units>B</units>
<description>The free space of swap volume/file in bytes.</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
</item>
<item>
<name>Free swap space in %</name>
<type>ZABBIX_ACTIVE</type>
<key>system.swap.size[,pfree]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<value_type>FLOAT</value_type>
<units>%</units>
<description>The free space of swap volume/file in percent.</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
</item>
<item>
<name>Total swap space</name>
<type>ZABBIX_ACTIVE</type>
<key>system.swap.size[,total]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<status>DISABLED</status>
<units>B</units>
<description>The total space of swap volume/file in bytes.</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
</item>
<item>
<name>System description</name>
<type>ZABBIX_ACTIVE</type>
<key>system.uname</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>0</trends>
<status>DISABLED</status>
<value_type>CHAR</value_type>
<description>System description of the host.</description>
<applications>
<application>
<name>General</name>
</application>
</applications>
<preprocessing>
<step>
<type>DISCARD_UNCHANGED_HEARTBEAT</type>
<params>1d</params>
</step>
</preprocessing>
</item>
<item>
<name>Uptime</name>
<type>ZABBIX_ACTIVE</type>
<key>system.uptime</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<units>uptime</units>
<description>System uptime in 'N days, hh:mm:ss' format.</description>
<applications>
<application>
<name>Status</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{last()}<10m</expression>
<name>Host has been restarted (uptime < 10m)</name>
<priority>WARNING</priority>
<description>The device uptime is less than 10 minutes.</description>
<manual_close>YES</manual_close>
</trigger>
</triggers>
</item>
<item>
<name>Current Size of Volume - VOL_SYS</name>
<type>ZABBIX_ACTIVE</type>
<key>vfs.dir.size[c:\siemens\vol_sys]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>B</units>
<description>tech.notes. zabbix agent should have access to monitoring folder!</description>
<applications>
<application>
<name>Storage Information</name>
</application>
</applications>
</item>
<item>
<name>Free Space of Disk C</name>
<type>ZABBIX_ACTIVE</type>
<key>vfs.fs.size[C:,free]</key>
<delay>15s</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>B</units>
<applications>
<application>
<name>Storage Information</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{last()}<={$STORAGELEVEL.DANGER}</expression>
<name>The volume on {HOST.NAME} is full!</name>
<url>https://docs.sw.siemens.com/en-US/product/282219420/doc/PL20190708094221054.plm00102/html/xid364226</url>
<priority>DISASTER</priority>
<description>You should check your storage with Teamcenter volumes!</description>
<manual_close>YES</manual_close>
</trigger>
<trigger>
<expression>{last(20m)}<={$STORAGELEVEL.WARNING}</expression>
<name>The volume on {HOST.NAME} is partially full!</name>
<url>https://docs.sw.siemens.com/en-US/product/282219420/doc/PL20190708094221054.plm00102/html/xid364226</url>
<priority>AVERAGE</priority>
<description>You should check your storage with Teamcenter volumes!</description>
<manual_close>YES</manual_close>
</trigger>
</triggers>
</item>
<item>
<name>Total Space of Disk C</name>
<type>ZABBIX_ACTIVE</type>
<key>vfs.fs.size[C:,total]</key>
<delay>15s</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>B</units>
<applications>
<application>
<name>Storage Information</name>
</application>
</applications>
</item>
<item>
<name>Total memory</name>
<type>ZABBIX_ACTIVE</type>
<key>vm.memory.size[total]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<units>B</units>
<description>Total memory in Bytes</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
</item>
<item>
<name>Used memory</name>
<type>ZABBIX_ACTIVE</type>
<key>vm.memory.size[used]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<units>B</units>
<description>Used memory in Bytes</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
</item>
<item>
<name>Memory utilization</name>
<type>CALCULATED</type>
<key>vm.memory.util</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>{$TREND}</trends>
<value_type>FLOAT</value_type>
<units>%</units>
<params>last("vm.memory.size[used]") / last("vm.memory.size[total]") * 100</params>
<description>Memory utilization in %</description>
<applications>
<application>
<name>Memory</name>
</application>
</applications>
<triggers>
<trigger>
<expression>{min(5m)}>{$MEMORY.UTIL.MAX}</expression>
<name>High memory utilization ( >{$MEMORY.UTIL.MAX}% for 5m)</name>
<priority>AVERAGE</priority>
<description>The system is running out of free memory.</description>
</trigger>
</triggers>
</item>
<item>
<name>Physical disks WMI get</name>
<type>ZABBIX_ACTIVE</type>
<key>wmi.getall[root\cimv2,"select * from win32_perfformatteddata_perfdisk_physicaldisk"]</key>
<delay>{$UPDATE}</delay>
<history>{$HISTORY}</history>
<trends>0</trends>
<status>DISABLED</status>
<value_type>TEXT</value_type>
<description>Raw data of win32_perfformatteddata_perfdisk_physicaldisk.</description>
<applications>
<application>
<name>Zabbix raw items</name>
</application>
</applications>
</item>
</items>
<discovery_rules>
<discovery_rule>
<name>Windows services discovery</name>
<type>ZABBIX_ACTIVE</type>
<key>service.discovery</key>
<delay>1h</delay>
<filter>
<evaltype>AND</evaltype>
<conditions>
<condition>
<macro>{#SERVICE.NAME}</macro>
<value>{$SERVICE.NAME.MATCHES}</value>
<formulaid>A</formulaid>
</condition>
<condition>
<macro>{#SERVICE.NAME}</macro>
<value>{$SERVICE.NAME.NOT_MATCHES}</value>
<operator>NOT_MATCHES_REGEX</operator>
<formulaid>B</formulaid>
</condition>
<condition>
<macro>{#SERVICE.STARTUPNAME}</macro>
<value>{$SERVICE.STARTUPNAME.MATCHES}</value>
<formulaid>C</formulaid>
</condition>
<condition>
<macro>{#SERVICE.STARTUPNAME}</macro>
<value>{$SERVICE.STARTUPNAME.NOT_MATCHES}</value>
<operator>NOT_MATCHES_REGEX</operator>
<formulaid>D</formulaid>
</condition>
</conditions>
</filter>
<description>Discovery of Windows services of different types as defined in template's macros.</description>