IT360 Best Practices - A guideline

This section discusses some of the best practices for IT360.

For Performance Tuning aspects of IT360 Best Practices, please refer to the link: https://manageengineit360.wiki.zoho.com/IT360-Best-Practices-Guide.html

  1. Meeting system requirements

  2. It is suggested that you strictly follow the hardware and software / OS requirements as outlined in the following link and thereby avoid product hanging / crashing issues.

    http://www.manageengine.com/it360/help/meitms/setup-meit360/system_requirements.html

  3. Installing Central Server and Probes

  4. Using VMs

    All editions of IT360 can be installed in a VM environment and it needs to meet the System Requirements as per point 1 above. You may use VMs when you wanto reduce the number of physical server / boxes.

  5. Be ready with the IT360 Prerequisites before Implementation

  6. To ensure a smooth user and functional and implementation experience, we recommend you to follow and comply with the prerequisites outlined in our help document.

    http://www.manageengine.com/it360/help/meitms/setup-meit360/prerequisites-intro.html

    These mostly relate to

  7. Access Privileges [Access Privileges is one of the most important but often forgotten aspect of a successful Implementation and Post Implementation phase.Checking the credentials / Access Privileges / username-password is one of the first few things that we would ask you to confirm during any troubleshooting session with our support team]
  8. Third Party jar files

  9. Port availability / readiness

  10. WMI [RPC, DCOM settings]

  11. DNS configuration

  12. Excluding AV scans

  13. Device reachability

  14. SMS (Text Message) modem usage

  15. Exchange Server, etc.

  16. Network Speed / Connectivity

  17. It is a good practice to keep a constant watch on the network / bandwidth speed with respect to the following scenarios:

  18. Failover and MSSQL

    If you plan to use the Failover option offered by IT360, it is recommended to use MSSQL as the backend database.

  19. Understanding Clients' Environment

  20. If you are an MSP, offering services using IT360, it is suggested to understand your client's environment and discuss the same with our support team so as to assist you with handling any typical situations, very specific to this client.

  21. IP Address clash

  22. This happens typically in a multi-customer, MSP environment that uses a shared IT360 Probe. When you have two machines of same IP addresses from a single customer or different customers, one of the machines will have to be monitored through a different Probe.

  23. Security and Connectivity and Device reachability concerns in a typical MSP environment

  24. You may use the NAT support offered in IT360 when communication / reachability between the Central Server and Probes [or with the devices] needs to happen over the internet. This feature is particulary useful for MSPs

  25. Support Information File and Screen shots

  26. Whenever you want to report a problem to our support team, it is a good practice to send us a screen shot and also the log files. Also, ensure to tell us the scenario / environment / situation clearly, when you face a problem. You may send us the complete Support Information File that is automatically generated by the click of a hyper link [the Support -- Create Support File link on the top right corner of IT360 UI]. You may email us the same. Where the log files and screen shots are huge, of the order of several MBs, we suggest you to ftp / upload them to one of our public servers, the details of which are available in the above mentioned Support page.

  27. Backup and Disaster Recovery

  28. It is a good practice to take periodic backup of the databases and the configuration files. For details, please refer to the following link:

    https://manageengineit360.wiki.zoho.com/Data-Backup-and-Restoration.html

  29. Scalability considerations: Time to use a new Probe, Time to use a new Central Server

  30. It is advised not to overload a Probe or a Central Server beyond its recommended scalability.

    It is recommended to install / use a new probe when it crosses the following limits:

    It is recommended to use a new Central Server, when the load on it crosses the following limits [sum of all the probes put-together]:

    Please note thar the load on the server also depends on the Polling interval, etc., and hence it is advisable to take the help of our Support team on arriving at the final numbers.

  31. Ensuring Continuity

    When your requirement is to ensure an uninterupted monitoring and managment of your network using IT360, it is good to use the Failover feature.

  32. Managing Users and Roles in IT360

    IT360 has several modules - the Network Devices module, Netflow / Bandwidth module, the Apppilcations and Servers module and the ServiceDesk module. You may want to provide restricted access to these module to a number of Users in varying permutations. The Users and Roles feature helps you do this and it is advised to understand this feature before configuration of the same. Please refer to the following link for details:

  33. http://www.manageengine.com/it360/help/meitms/getting-started/manage_users_roles.html

  34. User Synchronisation frequency from Active Directory

  35. Frequency of User synchronisation or importing Users from Active Directory should not be less than 1 day. You may configure this Admin -- General -- Active Directory -- Import Users from Active Directory

  36. Other best practices

    Some of the other areas where you could do some fine tuning / optimisation / follow best practices are listed here:
  37. FAQ and Troubleshooting

Please refer to the following sections of the Help Documentation for FAQ and Troubleshooting [these could also be a source of best practices tips]:

FAQ: http://www.manageengine.com/it360/help/meitms/faq-it360.html

Troubleshooting: http://www.manageengine.com/it360/help/meitms/troubleshoot.html

Applications and Servers - Best Practices

  1. Using Downtime Scheduler

    One way of improving the performance of the Applications and Servers module of IT360 is to use the Downtime Scheduler feature, for such of those servers for which you may want to have a scheduled maintenance: the Data Collection Threads are freed during the scheduled downtimes. These threads can be utilised by other monitors. [Note: Using the Downtime Scheduler feature also avoids the generation of alert notifications during the planned maintenance]

  2. Polling Interval

    IT360 offers two distinct features related to Polling:

  3. Fault Management

  4. Socket Timeout

    One way of reducing the false alarms is to increase the socket timeout option by changing the am.sockettest.timeout value present in <IT360_Home>/applications/conf/AMServer.properties. You may change the value from 5 to say, 10.

    Network Availability check

    When you use IT360 for network device monitoring, alarms are generated when the url is not available / down. However, you may also see alarms when IT360 is out of network or if the proxy settings are not configured. To avoid such false alarms, you may use the Network Availabilty Check option where you specify a dependable host which is unlikely to go unreachable / go down. Before reporting a monitored resource as down, IT360 checks for the availability of this specified resource and if it is down only then it reports the monitored devices as down.

    URL Availability Check

    When you use IT360 for URL monitoring, alarms are generated when the url is not available / down. However, you may also see alarms when IT360 is out of network or if the proxy settings are not configured. To avoid such false alarms, you may use the URL Availabilty Check option where you specify a dependable URL which is unlikely to go down. Before reporting a monitored url as down, IT360 checks for the availability of this specified url and if it is down only then it reports the monitored url as down.

    Consecutive Polls check

    You may use this option to check the number of consecutive polls for which an error existed before actually reporting the error to the IT360 system for alarm notification, etc..You need to configure at Admin -- Servers and Applications -- Alarm Settings --Consecutive Polls Count

  5. Log file management

  6. You may also specify the size of the log files at <IT360_Home>/applications/working/conf/logging_parameters.conf

Networks - Best Practices

  1. Ping Timeout

    When ping timeout happens, the devices are not discovered. You may increase the Timeout value to try and discover the devices. The Timeout value can be set in the following file:

    <IT360_Home>/networks/conf/ping.properties

  2. Identifying the devices by their Host Names

    If you want to identify the devices by their Host Names instead of their IP Addresses, you need to set the DNS Server address in the machine that hosts IT360.

  3. Creating new device templates and importing the new MIBs

It360 supports monitoring of several hundreds of devices across vendors. The corresponding Devices Templates and MIBs are already present in IT360, by default. However, if you want to monitor a New Device [which is outside of the Device Templates list], it is a good practice to create a New Device Template and import the relevant MIBs, well ahead of its monitoring by IT360. This ensures that the New Device is placed under the correct device category.

Performance Tuning aspects of IT360

For Database tuning, Heap size, thread cache, query cache settings, etc., please refer to the following link. This link contains complete details about the tuning aspects of IT360 for optimal performance.

https://manageengineit360.wiki.zoho.com/IT360-Best-Practices-Guide.html



Copyright © 2014, ZOHO Corp. All Rights Reserved.