Ad Widget

Collapse

Active Check Not Working

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jasonw
    Junior Member
    • Oct 2013
    • 25

    #1

    Active Check Not Working

    I have a check on a Windows Server 2012 host in a template defined as:

    perf_counter["\LogicalDisk({#FSNAME})\Avg. Disk sec/Read"]

    And it seems to be working fine... So, I CLONED this check, changed the title and the counter to this:

    perf_counter["\LogicalDisk({#FSNAME})\Avg. Disk sec/Write"]

    (Note WRITE instead of READ)... For whatever reason, the agent never picks up the check... I even tried to re-write it as:

    perf_counter[\236({#FSNAME})\210]

    I've even stopped and restarted the agent, and looked at the debug output:

    696:20131104:090101.021 sending [{
    "request":"active checks",
    "host":"SERVERNAME"}]
    696:20131104:090101.021 before read
    696:20131104:090101.039 got [{
    "response":"success",
    "data":[
    {
    "key":"perf_counter[\"\\LogicalDisk(C\\Avg. Disk sec\/Read\"]",
    "delay":30,
    "lastlogsize":0,
    "mtime":0},
    {
    "key":"perf_counter[\\236(C\\1482]",
    "delay":60,
    "lastlogsize":0,
    "mtime":0},
    {
    "key":"perf_counter[\\4\\56]",
    "delay":30,
    "lastlogsize":0,
    "mtime":0},
    {
    "key":"perf_counter[\\4\\58]",
    "delay":30,
    "lastlogsize":0,
    "mtime":0},
    {
    "key":"system.cpu.load[,avg1]",
    "delay":60,
    "lastlogsize":0,
    "mtime":0},
    {
    "key":"vfs.fs.discovery",
    "delay":3600,
    "lastlogsize":0,
    "mtime":0},
    {
    "key":"vfs.fs.size[C:,free]",
    "delay":3600,
    "lastlogsize":0,
    "mtime":0},
    {
    "key":"vfs.fs.size[C:,pfree]",
    "delay":3600,
    "lastlogsize":0,
    "mtime":0},
    {
    "key":"vfs.fs.size[C:,total]",
    "delay":3600,
    "lastlogsize":0,
    "mtime":0},
    {
    "key":"vfs.fs.size[C:,used]",
    "delay":3600,
    "lastlogsize":0,
    "mtime":0}]}]
    696:20131104:090101.039 In parse_list_of_checks()

    Notice that it never receives the check. What is going on here?

    In case it makes a difference, this is a check defined as an Item Prototype on a Mounted Filesystem Discovery rule...
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    Note that any changes you make to discovery rules take upwards of an hour to take effect.

    Comment

    Working...