Ad Widget

Collapse

netapp and exchange monitoring

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Magician
    Junior Member
    • Mar 2013
    • 11

    #1

    netapp and exchange monitoring

    hi,

    i have zabbix 2.0.5 and i have exchange 2010 and netapp .

    now i installed all the templates but because of our configuration in the exchange i dont know how to monitor the space.

    we have a hosted exchange , with 20 DBS to every client , now all the DBS are sitting on luns in the netapp that is configured to a directory .

    meaning : [email protected] [email protected] [email protected]
    so its like:
    d:\lun\a
    d:\lun\b
    d:\lun\c

    now to each of those folders in the disk managemnt of windows 2008 r2 you have a disk connected to it .

    in the disk management i see the volume list + % free .

    how can i add a correct trigger to spot the limit i configure for each company.

    i dont know where to define the threshold and trigger - basically i believe that if you direct me to where i need ot build the threshold i can create the right trigger .

    hope you understood , if not ill help with pictures to explain myself better .
  • Magician
    Junior Member
    • Mar 2013
    • 11

    #2
    i`ve added a picture to explain better
    Attached Files

    Comment

    • steveboyson
      Senior Member
      • Jul 2013
      • 582

      #3
      Install and configure a 2.x zabbix_agent (zabbix_agentd.exe) on your windows box, start the service and then post the output of

      Code:
      zabbix_get -s <your-windows-server> -k vfs.fs.discovery
      Execute that on your Zabbix server.

      It should give something like:
      Code:
      zabbix:~ # zabbix_get -s servername -k vfs.fs.discovery
      {
              "data":[
                      {
                              "{#FSNAME}":"A:",
                              "{#FSTYPE}":"UNKNOWN"},
                      {
                              "{#FSNAME}":"C:",
                              "{#FSTYPE}":"NTFS"},
                      {
                              "{#FSNAME}":"Z:",
                              "{#FSTYPE}":"UNKNOWN"}]}
      Knowing that, we can help you further.

      Comment

      • Magician
        Junior Member
        • Mar 2013
        • 11

        #4
        thanks , but in the syntax i see a: , c: , z: - our system is per folder not per drive , should still work ?

        Comment

        • steveboyson
          Senior Member
          • Jul 2013
          • 582

          #5
          Originally posted by Magician
          thanks , but in the syntax i see a: , c: , z: - our system is per folder not per drive , should still work ?
          Just try it, it autodiscovers your disks.

          As long as these are really "disks" as seen from the operating system this will work.

          Comment

          • steveboyson
            Senior Member
            • Jul 2013
            • 582

            #6
            That means your disks need to be visible in the "disk management "MMC console.
            If that is not the case, you cannot use the "disks autodiscovery".

            Then you have to implement a custom action (which means you have to code something in Powershell, VB, WSH, perl or whatever you prefer).

            Comment

            • Magician
              Junior Member
              • Mar 2013
              • 11

              #7
              "data":[
              {
              "{#FSNAME}":"*:",
              "{#FSTYPE}":"UNKNOWN"},
              {
              "{#FSNAME}":"*:",
              "{#FSTYPE}":"NTFS"},
              {
              "{#FSNAME}":"*:",
              "{#FSTYPE}":"NTFS"},
              {
              "{#FSNAME}":"*:",
              "{#FSTYPE}":"UNKNOWN"}]}

              well it doesnt give the volumes , just this list .

              so it means i need to create custom action , so it brings me to two things :

              1. i remind you its a storage and perhaps we can test it from the storage point of view - i have netapp template which we can use - if that an option ofcourse

              2. if we couldnt use the netapp template, anyway where i can start with the process of making a script ? , the script should be something like :
              discover the volumes and spaces , put them in a list , and create a trigger to see this list/file .
              is it right or i need to think on other direction ?

              thanks .

              Comment

              • steveboyson
                Senior Member
                • Jul 2013
                • 582

                #8
                I would write a custom disocvery script which spits out:

                Code:
                {
                        "data":[
                                {
                                        "{#FSNAME}":"L:\USERDIR\USER_A",
                                        "{#FSTYPE}":"EXCHANGE"},
                                {
                                        "{#FSNAME}":"L:\USERDIR\USER_B",
                                        "{#FSTYPE}":"EXCHANGE"},
                                {
                                        "{#FSNAME}":"L:\USERDIR\USER_C",
                                        "{#FSTYPE}":"EXCHANGE"}
                ]}
                and so on.

                Then you could define a regexp for macro "{#FSNAME}" to include/exclude needed user directories. You might even add your regular disks to this self-written discovery which then have a different #FSTYPE, so you can exclude/include on that macro as well.

                Comment

                • Magician
                  Junior Member
                  • Mar 2013
                  • 11

                  #9
                  if the agent returns other values, which script could give me that data return ?

                  Comment

                  • steveboyson
                    Senior Member
                    • Jul 2013
                    • 582

                    #10
                    As I wrote before, you probably should code your own script. I doubt that there exists a script for your special needs.

                    Comment

                    Working...