checks:
  Network_Nebraska_-_Latency_-_Loss-forward:
    added_by_psconfig: 1
    checkInterval: 1800
    description: Queries an esmond MA for one-way loss data and alerts on response
    name: Packet Loss
    params:
      command:
        162.127.1.1:
          default: /usr/lib64/nagios/plugins/check_loss.pl -u %maUrl -s %row.map.address -4 -d %col.map.address -r 2700 -c 0.1 -w 0.001 -t 60
        162.127.1.5:
          default: /usr/lib64/nagios/plugins/check_loss.pl -u %maUrl -s %row.map.address -4 -d %col.map.address -r 2700 -c 0.1 -w 0.001 -t 60
        162.127.1.61:
          default: /usr/lib64/nagios/plugins/check_loss.pl -u %maUrl -s %row.map.address -4 -d %col.map.address -r 2700 -c 0.1 -w 0.001 -t 60
        162.127.1.81:
          default: /usr/lib64/nagios/plugins/check_loss.pl -u %maUrl -s %row.map.address -4 -d %col.map.address -r 2700 -c 0.1 -w 0.001 -t 60
        162.127.1.85:
          default: /usr/lib64/nagios/plugins/check_loss.pl -u %maUrl -s %row.map.address -4 -d %col.map.address -r 2700 -c 0.1 -w 0.001 -t 60
      graphUrl:
        162.127.1.1:
          default: /perfsonar-graphs/graphWidget.cgi?source=%row.map.address&dest=%col.map.address&displaysetdest=%col.displayset&url=%maUrl&reverseurl=%maUrlReverse&displaysetsrc=%row.displayset
        162.127.1.5:
          default: /perfsonar-graphs/graphWidget.cgi?source=%row.map.address&dest=%col.map.address&displaysetdest=%col.displayset&url=%maUrl&reverseurl=%maUrlReverse&displaysetsrc=%row.displayset
        162.127.1.61:
          default: /perfsonar-graphs/graphWidget.cgi?source=%row.map.address&dest=%col.map.address&displaysetdest=%col.displayset&url=%maUrl&reverseurl=%maUrlReverse&displaysetsrc=%row.displayset
        162.127.1.81:
          default: /perfsonar-graphs/graphWidget.cgi?source=%row.map.address&dest=%col.map.address&displaysetdest=%col.displayset&url=%maUrl&reverseurl=%maUrlReverse&displaysetsrc=%row.displayset
        162.127.1.85:
          default: /perfsonar-graphs/graphWidget.cgi?source=%row.map.address&dest=%col.map.address&displaysetdest=%col.displayset&url=%maUrl&reverseurl=%maUrlReverse&displaysetsrc=%row.displayset
      maUrl:
        162.127.1.1:
          default: https://162.127.1.1/esmond/perfsonar/archive
        162.127.1.5:
          default: https://162.127.1.5/esmond/perfsonar/archive
        162.127.1.61:
          default: https://162.127.1.61/esmond/perfsonar/archive
        162.127.1.81:
          default: https://162.127.1.81/esmond/perfsonar/archive
        162.127.1.85:
          default: https://162.127.1.85/esmond/perfsonar/archive
    retryAttempts: 1
    retryInterval: 300
    timeout: 60
    type: net.es.maddash.checks.PSNagiosCheck
  Network_Nebraska_-_Throughput_-_Throughput-forward:
    added_by_psconfig: 1
    checkInterval: 14400
    description: Queries an esmond MA for throughput data and alerts on response
    name: Throughput
    params:
      command:
        162.127.1.1:
          default: '/usr/lib64/nagios/plugins/check_throughput.pl -u %maUrl -s %row.map.address -p tcp -4 -d %col.map.address -r 86400 -c .03: -w .04: --udpbandwidth 52428800 -t 60'
        162.127.1.5:
          default: '/usr/lib64/nagios/plugins/check_throughput.pl -u %maUrl -s %row.map.address -p tcp -4 -d %col.map.address -r 86400 -c .03: -w .04: --udpbandwidth 52428800 -t 60'
        162.127.1.61:
          default: '/usr/lib64/nagios/plugins/check_throughput.pl -u %maUrl -s %row.map.address -p tcp -4 -d %col.map.address -r 86400 -c .03: -w .04: --udpbandwidth 52428800 -t 60'
        162.127.1.81:
          default: '/usr/lib64/nagios/plugins/check_throughput.pl -u %maUrl -s %row.map.address -p tcp -4 -d %col.map.address -r 86400 -c .03: -w .04: --udpbandwidth 52428800 -t 60'
        162.127.1.85:
          default: '/usr/lib64/nagios/plugins/check_throughput.pl -u %maUrl -s %row.map.address -p tcp -4 -d %col.map.address -r 86400 -c .03: -w .04: --udpbandwidth 52428800 -t 60'
      graphUrl:
        162.127.1.1:
          default: /perfsonar-graphs/graphWidget.cgi?source=%row.map.address&dest=%col.map.address&displaysetdest=%col.displayset&url=%maUrl&reverseurl=%maUrlReverse&displaysetsrc=%row.displayset
        162.127.1.5:
          default: /perfsonar-graphs/graphWidget.cgi?source=%row.map.address&dest=%col.map.address&displaysetdest=%col.displayset&url=%maUrl&reverseurl=%maUrlReverse&displaysetsrc=%row.displayset
        162.127.1.61:
          default: /perfsonar-graphs/graphWidget.cgi?source=%row.map.address&dest=%col.map.address&displaysetdest=%col.displayset&url=%maUrl&reverseurl=%maUrlReverse&displaysetsrc=%row.displayset
        162.127.1.81:
          default: /perfsonar-graphs/graphWidget.cgi?source=%row.map.address&dest=%col.map.address&displaysetdest=%col.displayset&url=%maUrl&reverseurl=%maUrlReverse&displaysetsrc=%row.displayset
        162.127.1.85:
          default: /perfsonar-graphs/graphWidget.cgi?source=%row.map.address&dest=%col.map.address&displaysetdest=%col.displayset&url=%maUrl&reverseurl=%maUrlReverse&displaysetsrc=%row.displayset
      maUrl:
        162.127.1.1:
          default: https://162.127.1.1/esmond/perfsonar/archive
        162.127.1.5:
          default: https://162.127.1.5/esmond/perfsonar/archive
        162.127.1.61:
          default: https://162.127.1.61/esmond/perfsonar/archive
        162.127.1.81:
          default: https://162.127.1.81/esmond/perfsonar/archive
        162.127.1.85:
          default: https://162.127.1.85/esmond/perfsonar/archive
    retryAttempts: 1
    retryInterval: 300
    timeout: 60
    type: net.es.maddash.checks.PSNagiosCheck
dashboards:
  -
    added_by_psconfig: 1
    grids:
      -
        name: 'Network Nebraska - Latency - Loss'
      -
        name: 'Network Nebraska - Throughput - Throughput'
    name: Network Nebraska
database: /var/lib/maddash/
grids:
  -
    added_by_psconfig: 1
    checks:
      - Network_Nebraska_-_Latency_-_Loss-forward
    colOrder: alphabetical
    columnAlgorithm: all
    columns: Network_Nebraska_-_Latency-col
    excludeSelf: 1
    name: 'Network Nebraska - Latency - Loss'
    report: ps-nagios-loss_1
    rowOrder: alphabetical
    rows: Network_Nebraska_-_Latency-row
    statusLabels:
      critical: Loss rate is >= 0.1%
      notrun: Check has not run yet
      ok: Loss rate is <= 0.001%
      unknown: Unable to find test data
      warning: Loss rate is > 0.001%
  -
    added_by_psconfig: 1
    checks:
      - Network_Nebraska_-_Throughput_-_Throughput-forward
    colOrder: alphabetical
    columnAlgorithm: all
    columns: Network_Nebraska_-_Throughput-col
    excludeSelf: 1
    name: 'Network Nebraska - Throughput - Throughput'
    report: ps-nagios-throughput_1
    rowOrder: alphabetical
    rows: Network_Nebraska_-_Throughput-row
    statusLabels:
      critical: Throughput <= .03Gbps
      notrun: Check has not run yet
      ok: Throughput >= .04Gbps
      unknown: Unable to find test data
      warning: Throughput < .04Gbps
groupMembers:
  -
    added_by_psconfig: 1
    id: 162.127.1.5
    label: Lincoln
    map:
      default:
        address: 162.127.1.5
        host_id: 162.127.1.5
    pstoolkiturl: http://162.127.1.5/toolkit/
  -
    added_by_psconfig: 1
    id: 162.127.1.1
    label: Omaha
    map:
      default:
        address: 162.127.1.1
        host_id: 162.127.1.1
    pstoolkiturl: http://162.127.1.1/toolkit/
  -
    added_by_psconfig: 1
    id: 162.127.1.85
    label: Scottsbluff
    map:
      default:
        address: 162.127.1.85
        host_id: 162.127.1.85
    pstoolkiturl: http://162.127.1.85/toolkit/
  -
    added_by_psconfig: 1
    id: 162.127.1.81
    label: Kearney
    map:
      default:
        address: 162.127.1.81
        host_id: 162.127.1.81
    pstoolkiturl: http://162.127.1.81/toolkit/
  -
    added_by_psconfig: 1
    id: 162.127.1.61
    label: Grand Island
    map:
      default:
        address: 162.127.1.61
        host_id: 162.127.1.61
    pstoolkiturl: https://162.127.1.61/toolkit/
groups:
  Network_Nebraska_-_Latency-col:
    - 162.127.1.1
    - 162.127.1.81
    - 162.127.1.85
    - 162.127.1.61
    - 162.127.1.5
  Network_Nebraska_-_Latency-row:
    - 162.127.1.1
    - 162.127.1.81
    - 162.127.1.85
    - 162.127.1.61
    - 162.127.1.5
  Network_Nebraska_-_Throughput-col:
    - 162.127.1.1
    - 162.127.1.81
    - 162.127.1.85
    - 162.127.1.61
    - 162.127.1.5
  Network_Nebraska_-_Throughput-row:
    - 162.127.1.1
    - 162.127.1.81
    - 162.127.1.85
    - 162.127.1.61
    - 162.127.1.5
http:
  port: 8881
reports:
  -
    id: loss_mesh_report
    rule:
      rules:
        -
          match:
            status: 3
            type: status
          problem:
            category: CONFIGURATION
            message: Grid is down
            severity: 3
            solutions:
              - 'If you just configured this grid, you may just need to wait as it takes a few minutes for loss data to populate'
              - Verify maddash is configured properly. Look in the files under /var/log/maddash/ for any errors. Things to look for are incorrect paths to checks or connection errors.
              - Verify that the pSConfig MaDDash Agent has run recently and you are looking at an accurate test configuration
              - Verify that your measurement archive(s) are running
              - Verify no firewall is blocking maddash from reaching your measurement archive(s)
              - Verify your hosts are downloading the pSConfig file and that there are tasks listed when you run 'psconfig pscheduler-tasks'
              - Verify that pSConfig pScheduler Agent is running ('systemctl status psconfig-pscheduler-agent')
              - Verify your hosts are able to reach their configured measurement archive and that there are no errors in /var/log/perfsonar/psconfig-pscheduler-agent.log
          selector:
            type: grid
          type: rule
        -
          match:
            status: 0
            type: status
          problem:
            category: PERFORMANCE
            message: Entire grid has OK status
            severity: 0
          selector:
            type: grid
          type: rule
        -
          rule:
            rules:
              -
                match:
                  status: 3
                  type: status
                problem:
                  category: CONFIGURATION
                  message: Site is down
                  severity: 3
                  solutions:
                    - Verify the host is up
                    - 'If recently added to the configuration, verify the pSConfig file has been downloaded by the end-hosts since the update.'
                    - 'If recently removed from the configuration, verify that the pSConfig MaDDash Agent has run recently and you are looking at an accurate test configuration'
                    - Verify the local and remote sites allow access to TCP port 861 and UDP ports 8760-9960
                selector:
                  type: site
                type: rule
              -
                match:
                  status: 3
                  type: status
                problem:
                  category: CONFIGURATION
                  message: Unable to run and/or query any outgoing one-way delay tests.
                  severity: 3
                  solutions:
                    - Verify you are not blocking any of the required outgoing OWAMP ports in your firewall
                    - Verify the remote sites allow your host to access UDP ports 8760-9960
                selector:
                  type: row
                type: rule
              -
                match:
                  status: 3
                  type: status
                problem:
                  category: CONFIGURATION
                  message: Unable to run and/or query any incoming one-way delay tests.
                  severity: 3
                  solutions:
                    - Verify your host and router firewalls are allowing UDP ports 8760-9960
                selector:
                  type: column
                type: rule
              -
                rules:
                  -
                    match:
                      statuses:
                        - 0.0
                        - .5
                        - 1.0
                        - -1.0
                      threshold: .6
                      type: statusWeightedThreshold
                    problem:
                      category: PERFORMANCE
                      message: Outgoing loss is above warning or critical thresholds to a majority of sites
                      severity: 2
                    selector:
                      type: row
                    type: rule
                  -
                    match:
                      statuses:
                        - 0.0
                        - .5
                        - 1.0
                        - -1.0
                      threshold: .6
                      type: statusWeightedThreshold
                    problem:
                      category: PERFORMANCE
                      message: Incoming loss is above warning or critical thresholds to a majority of sites
                      severity: 2
                    selector:
                      type: column
                    type: rule
                type: matchAll
            type: matchFirst
          type: forEachSite
      type: matchFirst
  -
    added_by_psconfig: 1
    id: ps-nagios-throughput_1
    rule:
      rules:
        -
          match:
            status: 3
            type: status
          problem:
            category: CONFIGURATION
            message: Grid is down
            severity: 3
            solutions:
              - 'If you just configured this grid in the configuration, you may just need to wait as it takes several hours for throughput data to populate (depending on the interval between tests)'
              - Verify maddash is configured properly. Look in the files under /var/log/maddash/ for any errors. Things to look for are incorrect paths to checks or connection errors.
              - Verify that pSConfig MaDDash Agent has run recently and you are looking at an accurate test configuration
              - Verify that your measurement archive(s) are running
              - Verify no firewall is blocking maddash from reaching your measurement archive(s)
              - Verify your hosts are downloading the pSConfig file and that there are tasks defined in command 'psconfig pscheduler-tasks'
              - Verify that psconfig-pscheduler-agent is running ('systemctl status psconfig-pscheduler-agent')
              - Verify your hosts are able to reach their configured measurement archive and that there are no errors in /var/log/perfsonar/psconfig-pscheduler-agent.log
          selector:
            type: grid
          type: rule
        -
          match:
            status: 0
            type: status
          problem:
            category: PERFORMANCE
            message: Entire grid has OK status.
            severity: 0
          selector:
            type: grid
          type: rule
        -
          rule:
            rules:
              -
                match:
                  status: 3
                  type: status
                problem:
                  category: CONFIGURATION
                  message: Site is down
                  severity: 3
                  solutions:
                    - Verify the host is up
                    - 'If recently added to the configuration, verify the pSConfig file has been downloaded by the end-hosts since the update. It may also take several hours for the first throughput test to run on this host.'
                    - 'If recently removed from the configuration, verify that the pSConfig MaDDash Agent has run recently and you are looking at an accurate test configuration'
                    - Verify NTP is synced on this host
                    - Verify the local and remote sites allow access to TCP port 443 and TCP/UDP port 5201
                selector:
                  type: site
                type: rule
              -
                match:
                  status: 3
                  type: status
                problem:
                  category: CONFIGURATION
                  message: Unable to run and/or query any outgoing throughput tests.
                  severity: 3
                  solutions:
                    - Verify you are not blocking any of the required outgoing throughput ports in your firewall
                    - Verify the remote sites allow your host to access TCP port 443 and TCP/UDP port 5201
                    - Verify the limits defined in /etc/pscheduler/limits.conf on each side are properly defined and not being exceeded by the tests
                selector:
                  type: row
                type: rule
              -
                match:
                  status: 3
                  type: status
                problem:
                  category: CONFIGURATION
                  message: Unable to run and/or query any incoming throughput tests.
                  severity: 3
                  solutions:
                    - Verify your host and router firewalls are allowing TCP port 443 and TCP/UDP port 5201
                    - Verify the limits defined in /etc/pscheduler/limits.conf are properly defined and not being exceeded by the tests
                selector:
                  type: column
                type: rule
              -
                rules:
                  -
                    match:
                      statuses:
                        - 0.0
                        - .5
                        - 1.0
                        - -1.0
                      threshold: .6
                      type: statusWeightedThreshold
                    problem:
                      category: PERFORMANCE
                      message: Outgoing throughput is below warning or critical thresholds to a majority of sites
                      severity: 2
                    selector:
                      type: row
                    type: rule
                  -
                    match:
                      statuses:
                        - 0.0
                        - .5
                        - 1.0
                        - -1.0
                      threshold: .6
                      type: statusWeightedThreshold
                    problem:
                      category: PERFORMANCE
                      message: Incoming throughput is below warning or critical thresholds to a majority of sites
                      severity: 2
                    selector:
                      type: column
                    type: rule
                type: matchAll
            type: matchFirst
          type: forEachSite
      type: matchFirst
  -
    added_by_psconfig: 1
    id: ps-nagios-loss_1
    rule:
      rules:
        -
          match:
            status: 3
            type: status
          problem:
            category: CONFIGURATION
            message: Grid is down
            severity: 3
            solutions:
              - 'If you just configured this grid, you may just need to wait as it takes a few minutes for loss data to populate'
              - Verify maddash is configured properly. Look in the files under /var/log/maddash/ for any errors. Things to look for are incorrect paths to checks or connection errors.
              - Verify that the pSConfig MaDDash Agent has run recently and you are looking at an accurate test configuration
              - Verify that your measurement archive(s) are running
              - Verify no firewall is blocking maddash from reaching your measurement archive(s)
              - Verify your hosts are downloading the pSConfig file and that there are tasks listed when you run 'psconfig pscheduler-tasks'
              - Verify that pSConfig pScheduler Agent is running ('systemctl status psconfig-pscheduler-agent')
              - Verify your hosts are able to reach their configured measurement archive and that there are no errors in /var/log/perfsonar/psconfig-pscheduler-agent.log
          selector:
            type: grid
          type: rule
        -
          match:
            status: 0
            type: status
          problem:
            category: PERFORMANCE
            message: Entire grid has OK status
            severity: 0
          selector:
            type: grid
          type: rule
        -
          rule:
            rules:
              -
                match:
                  status: 3
                  type: status
                problem:
                  category: CONFIGURATION
                  message: Site is down
                  severity: 3
                  solutions:
                    - Verify the host is up
                    - 'If recently added to the configuration, verify the pSConfig file has been downloaded by the end-hosts since the update.'
                    - 'If recently removed from the configuration, verify that the pSConfig MaDDash Agent has run recently and you are looking at an accurate test configuration'
                    - Verify the local and remote sites allow access to TCP port 861 and UDP ports 8760-9960
                selector:
                  type: site
                type: rule
              -
                match:
                  status: 3
                  type: status
                problem:
                  category: CONFIGURATION
                  message: Unable to run and/or query any outgoing one-way delay tests.
                  severity: 3
                  solutions:
                    - Verify you are not blocking any of the required outgoing OWAMP ports in your firewall
                    - Verify the remote sites allow your host to access UDP ports 8760-9960
                selector:
                  type: row
                type: rule
              -
                match:
                  status: 3
                  type: status
                problem:
                  category: CONFIGURATION
                  message: Unable to run and/or query any incoming one-way delay tests.
                  severity: 3
                  solutions:
                    - Verify your host and router firewalls are allowing UDP ports 8760-9960
                selector:
                  type: column
                type: rule
              -
                rules:
                  -
                    match:
                      statuses:
                        - 0.0
                        - .5
                        - 1.0
                        - -1.0
                      threshold: .6
                      type: statusWeightedThreshold
                    problem:
                      category: PERFORMANCE
                      message: Outgoing loss is above warning or critical thresholds to a majority of sites
                      severity: 2
                    selector:
                      type: row
                    type: rule
                  -
                    match:
                      statuses:
                        - 0.0
                        - .5
                        - 1.0
                        - -1.0
                      threshold: .6
                      type: statusWeightedThreshold
                    problem:
                      category: PERFORMANCE
                      message: Incoming loss is above warning or critical thresholds to a majority of sites
                      severity: 2
                    selector:
                      type: column
                    type: rule
                type: matchAll
            type: matchFirst
          type: forEachSite
      type: matchFirst
serverHost: localhost

