Advanced Alerting Configuration
      Back to home
      1. ProTop Knowledge Base
      2. Advanced Alerting Configuration

      Complete Your Advanced ProTop Configuration

      We've installed ProTop, and our databases are now being monitored. What's next?

      Once the basic ProTop installation and configuration are complete and communication between your ProTop installation and your ProTop Portal has been established and confirmed, it's time to move on to the Advanced ProTop configuration steps.

      Here is a comprehensive list of the advanced ProTop configuration procedures. You won't need all the optional procedures; please execute the ones that apply to you.

      NOTE: Be sure you've executed these procedures before you attempt to copy your initial ProTop installation to other servers.

      Advanced Configuration Procedures for All Installations:

      1. REMINDER: on Linux, add dbmonitor.sh to crontab of the user ID that runs ProTop
      2. REMINDER: be sure you have created at least the following localized versions of these default alert configuration files:
        cd $PROTOP/etc

        cp alert.cfg alert.[siteid].cfg

        cp pt3agent.cfg pt3agent.[siteid].cfg

        cp schedule.cfg schedule.[siteid].cfg
        Please make changes to your local versions rather than the default versions. This will prevent your customizations from being overwritten during the next ProTop update
      3. Adjust database table and index range parameters as recommended by ProTop RT
      4. Set up syncio in the scheduler - to measure and trend OE disk write performance
      5. Set up a user experience "client-server" monitor in the scheduler if you have remote users
      6. Set up a user experience "local host" in the scheduler
      7. schedule db analysis
      8. schedule automated health checks
      9. Add (df) disk space monitoring to your main db pt3agent.*.cfg
      10. Set up recurring outages in the ProTop Portal
      11. Set up alert responses and test/verify from the ProTop Portal
      12. Reduce alert noise, tune your alerts to your specific needs
      13. Set up Telegraf - for server metrics (not a ProTop tool; just on the most important server(s))

      Optional Advanced Configuration Procedures:

      1. Configure secure comms with the ProTop Portal
      2. Set up OE Replication monitoring
      3. If OE Replication+ is used, install ProTop on the target server and configure database monitoring
      4. If using shared memory connections, set up zOldTRXDetails.sh from .shx
      5. Set up Pro2 monitoring
      6. Set up Classic App Server / Webspeed monitoring
      7. Enable the calculation of uptime (System Availability) for critical databases
      8. Set up PASOE monitoring
      9. Set up log monitoring
      10. Set up custom application monitoring
      11. Check for NUMA issues if you are sharing a virtual host
      12. Configure custom alerts sent from your application
      13. Configure automated script actions initiated by alerts
      14. Manage database log files
      15. Create User Defined Key Performance Indicator metrics