Tuesday, May 7, 2013

Default SuperAgent Tweaks

Whenever I'm setting up a new SuperAgent system, there are always a few things I go through and do before I start data collection.  So, here's my list so I don't have to remember it:

  1. Add collectors by DNS - I like to add by NetBIOS name then click the IP button.  This helps me make sure I get the right IP address.  Then, after SA has done its check of the collector, I click the DNS button, which finds the DNS name from the IP address it previously resolved from the NetBIOS name.  This  double check makes sure I have the right server since the FQDN name should be fairly similar to the NetBIOS name.
  2. Add a port exclusion - Given the troubles I've had with large deployments and auto-discovery, I've decided to start adding a huge port exclusion from the get go.  I add 1025-65535 for the whole domain.  When/if I need to monitor an application in that range, I can always add an exception.  This can be done via the GUI or through a query:
    insert into application_rules
    (application_id,exclude_port_begin,exclude_port_end,rule_type)
    values (0,1025,65535,0);

    New in ADA 9.3! - This option can be enabled on each collector.  For standard collector or virtual collector, create a new text file: drive:\CA\bin\saConfigInterfaceRuntimeOptions.ini with the following line:
    /force positive config
    Then restart the CA ADA Monitor service.
  3. Add actions to the default incident responses - add all the possible actions to the incident responses. If I have the email address of the person/group that will be monitoring the SA for problems, I put an email action in the collection device default incident response.
  4. Create a 'No Response' network incident response - create this incident response with no actions.
  5. Adjust network types - I like to have only 4 network types: Internet - VPN, LAN, Not Rated, WAN.  I delete all the other network types.  Assign the Internet - VPN and Not Rated network types to the 'No Response' incident response created earlier.
  6. Edit the 'Weekends' maintenance schedule - Change the name to 'Full Time Maintenance' and change the period to all day, every day.  If there is a standing maintenance window that affects every server everywhere, add that period to the default.
  7. Change the data retention settings - Bump everything up to their max.  If it becomes a problem later on, I can always tune it down.
  8. Change the free space alarm - Change this from 5GB to 20GB and put somebody's email address in there.
  9. Import a networks list - I prefer to use the GXMLG, but at least understand regions if doing it by hand.  You can also use the standard private networks list if you have nothing to start with.
  10. Bump up the default observation numbers
    New in ADA 9.3! - You don't have to do this via direct database manipulation any more.  Just go to Administration >> Policies >> Performance Thresholds.  The middle table allows manipulation of the default threshold settings.  You can also setup the default threshold settings for the 'Not Rated' and 'Internet - VPN' network types; set them up for no thresholds on the network and combined thresholds.
  11. Import servers as subnets instead of individual servers - This just makes sense.  If possible, try to group servers together into subnets by application.  This makes it easier to assign groups of servers to an application.  If this isn't possible, enter the entire subnet.  
Those are all the tweaks I can think of at the moment.  If I think of any others, I'll add them to this list.