{"id":1518,"date":"2014-03-19T13:05:55","date_gmt":"2014-03-19T18:05:55","guid":{"rendered":"http:\/\/www.poweradmin.com\/blog\/?p=1518"},"modified":"2015-04-24T16:36:10","modified_gmt":"2015-04-24T21:36:10","slug":"server-monitoring-best-practices","status":"publish","type":"post","link":"https:\/\/www.poweradmin.com\/blog\/server-monitoring-best-practices\/","title":{"rendered":"Server Monitoring Best Practices"},"content":{"rendered":"<p><span style=\"margin-left: 20px; font-family: verdana,geneva;\"><iframe loading=\"lazy\" src=\"\/\/embed.gettyimages.com\/embed\/185265805?et=G1_AfzUy0UGisyvfrpRYmg&amp;sig=LWUB_z4REHNYqJBwMnLaW-1gpfzbuF5KbX81jALe2mY=\" width=\"300\" height=\"240\" frameborder=\"0\" scrolling=\"no\" align=\"right\"><\/iframe>As a business, you may be running many on-site or Web-based applications and services. Security, data handling, transaction support, load balancing, or the management of large distributed systems. The deployment of these will depend on the condition of your servers. So it\u2019s vital for you to continuously monitor their health and performance. <\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Here are some guidelines designed to help you get to grips with server monitoring and the implications that it carries.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\"> <\/span><\/p>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Understand Server Monitoring Basics<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">The basic elements of <a href=\"\/servermonitor\/\">server monitoring<\/a> are events, thresholds, notifications, and health.<\/span><\/p>\n<h3><span style=\"font-family: verdana,geneva;\"><strong>1. Events<\/strong><\/span><\/h3>\n<p><span style=\"font-family: verdana,geneva;\">Events are triggered on a system when a condition set by a given program occurs. An example would be when a service starts, or fails to start.<\/span><\/p>\n<h3><span style=\"font-family: verdana,geneva;\"><strong>2. Thresholds<\/strong><\/span><\/h3>\n<p><span style=\"font-family: verdana,geneva;\">A threshold is the point on a scale that must be reached, to trigger a response to an event. The response might be an alert, a notification, or a script being run.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Thresholds can be set by an application, or a user.<\/span><\/p>\n<h3><span style=\"font-family: verdana,geneva;\"><strong>3. Notifications<\/strong><\/span><\/h3>\n<p><span style=\"font-family: verdana,geneva;\">Notifications are the methods of informing an IT administrator that something (event, or response) has occurred.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Notifications can take many forms, such as:<\/span><\/p>\n<ul>\n<li><span style=\"font-family: verdana,geneva;\">Alerts in an application<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">E-mail messages<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Instant Messenger messages<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Dialog boxes on an IT administrator\u2019s screen<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Pager text messages<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Taskbar pop-ups<\/span><\/li>\n<\/ul>\n<h3><span style=\"font-family: verdana,geneva;\"><strong>4. Health<\/strong><\/span><\/h3>\n<p><span style=\"font-family: verdana,geneva;\">Health describes the set of related measurements defining the state of a variable being monitored.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">For instance, the overall health of a file server might be defined by read\/write disk access, CPU usage, network performance, and disk fragmentation.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\"><a title=\"\" href=\"\/servermonitor\/index.aspx?source=blog-centerad\" target=\"\" rel=\"\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1636 aligncenter\" style=\"border: 1px solid gray;\" title=\"PA Server Monitor 30 Day Free Trial\" src=\"\/blog\/wp-content\/uploads\/2013\/05\/image.png\" alt=\"PA Server Monitor 30 Day Free Trial\" width=\"336\" height=\"280\" srcset=\"https:\/\/www.poweradmin.com\/blog\/wp-content\/uploads\/2013\/05\/image.png 336w, https:\/\/www.poweradmin.com\/blog\/wp-content\/uploads\/2013\/05\/image-300x250.png 300w\" sizes=\"auto, (max-width: 336px) 100vw, 336px\"><\/a><\/span><\/p>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Set Clear Objectives<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\"><a title=\"\" href=\"\/blog\/wp-content\/uploads\/2014\/03\/server-monitoring-best-practices.jpg\" target=\"\" rel=\"\"><img loading=\"lazy\" decoding=\"async\" class=\"size-thumbnail wp-image-1685 alignright\" style=\"margin-left: 20px; border: 1px solid gray;\" title=\"Server Monitoring Best Practices\" src=\"\/blog\/wp-content\/uploads\/2014\/03\/server-monitoring-best-practices-150x150.jpg\" alt=\"Server Monitoring Best Practices\" width=\"150\" height=\"150\"><\/a>Decide what it is you need to monitor. Identify those events most relevant to detecting potential issues that could adversely affect operations or security.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">A checklist might include:<\/span><\/p>\n<ol start=\"1\" type=\"1\">\n<li><span style=\"font-family: verdana,geneva;\">Uptime and performance statistics of your web servers<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Web applications supported by your web servers<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Performance and user experience of your web pages, as supported by your web server<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">End-user connections to the server<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Measurements of load, traffic, and utilisation<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">A log of HTTP and HTTPS sessions and transactions<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">The condition of your server hardware<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Virtual Machines (VMs) and host machines running the web server<\/span><\/li>\n<\/ol>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Fit Solid Foundations<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">It\u2019s safe to say that most IT administrators appreciate useful data, clearly presented enabling them to view lots of information in a legible area. This means that you should take steps to ensure that your monitoring output is easy to read and well presented.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">A high-level \u201cdashboard\u201d can serve as a starting point. This should have controls for drilling down into more detail. Navigation around the monitoring tool and access to troubleshooting tools should be as transparent as possible.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">It\u2019s also necessary to:<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">\u2022 Identify the top variables to monitor, and set these as default values. Prioritise them in the user interface (UI).<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">\u2022 Provide preconfigured monitoring views that match situations encountered on a day-to-day basis.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">\u2022 Have a UI that also allows for easy customization.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">\u2022 Users\/IT managers should be able to choose what they want to monitor at any given time. Or be able to adjust the placement of their tools. And they should be able to decide the format they want to view the data in.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">\u2022 The UI text should be consistent, clear, concise, and professional. From the outset, it should state clearly what is being monitored \u2013 and what isn\u2019t.<\/span><\/p>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Build, to Scale<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\"><iframe loading=\"lazy\" src=\"\/\/embed.gettyimages.com\/embed\/463448299?et=SuJEsKzwJ0q18RUW7OmrNg&amp;sig=SWY4lwbvKnlY0i_eSPMHXW4wAAKCvRKOJH7cqKmoMGs=\" width=\"250\" height=\"312\" frameborder=\"0\" scrolling=\"no\" align=\"right\"><\/iframe>Organizations of different sizes naturally have different monitoring needs. Small Organization IT administrators often look to fix problems after they\u2019ve been identified. Monitoring is generally part of the troubleshooting process. Monitoring applications should intelligently identify problems, and notify the users via e-mail and other means. Keep the monitoring UI simple.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Medium Organization IT administrators monitor to isolate big and obvious problems. A monitoring system should provide an overview of the system, and explanations to help with the troubleshooting process. Preconfigured views, and the automation of common tasks performed on receiving negative monitoring information (e.g., ping, trace route.) will speed response. Again, keep the monitoring UI simple.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Large Organization\/Enterprise IT administrators require more detailed and specific information. Users may be dedicated exclusively to monitoring, and will appreciate dense data, with mechanisms for collaborating. Long-term ease of use will take precedence over ease of learning.<\/span><\/p>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Set Up Red Flags<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">You should provide a set of \u201cnormal\u201d or \u201crecommended\u201d values, as a baseline. This will give context to the information being monitored. The system may give the range of normal values itself, or provide tools for users to calculate their own.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Within the application, make sure that data representing normal performance can be captured. This can be used later, as a baseline for troubleshooting. In any case, users should be able to tell at a glance when a value is out of range, and is then a possible cause for concern. Your monitoring software can assist in this, by setting a standard alert scale, across the application.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">In Western cultures, common colors for system alerts are:<\/span><\/p>\n<ul>\n<li><span style=\"font-family: verdana,geneva;\">Red = Severe or Critical<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Yellow = Warning or Informational<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Green = Good or OK<\/span><\/li>\n<\/ul>\n<p><span style=\"font-family: verdana,geneva;\">For accessibility, colors should be combined with icons, for users who are sight-impaired. Words that can be dictated by a screen reader are also appropriate. Limit the use of custom icons in alerts though as users may resent having to learn too many new ones. There may also be conflicts with icons in other applications but saying that, common icons, that are recognizable, are fine, as there\u2019s nothing new to learn.<\/span><\/p>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Explain the Language<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">Don\u2019t assume that your users will understand all the information your monitoring software provides. Help them interpret the data, by providing explanations, in the user interface.<\/span><\/p>\n<ul>\n<li><span style=\"font-family: verdana,geneva;\">Use roll-overs to display specific data points, such as a critical spike in a chart<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Explain onscreen, how the monitoring view is filtered. For example, some variables or events might be hidden (but not necessarily trouble-free). The filter mechanism, an explanation of the filter, and the data itself should be positioned close together<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Give easy access to any variables that are excluded in a view<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">State when the last sample of data was captured<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Reference the data sources<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">There should be links to table, column, and row headings, with pop up explanations of the variables, abbreviations, and acronyms<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Provide links beside the tables themselves, with pop up explanations of the entire table<\/span><\/li>\n<\/ul>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Let Them Know<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">Alerts should be sent out, to indicate there is a problem with the system. Notifications should be informative enough to give IT administrators a starting point to address the problem. Information which helps the user take action should be displayed near the monitoring information. Probable causes and possible solutions should be prominently displayed.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Likewise, the tools needed for solving common problems should be easily accessible at the notification point.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">You should log 24 to 48 hours of data. That way, when a problem arises, users will have enough information available to troubleshoot. Note that some applications need longer periods of monitoring, and some shorter. The log length will be determined by the scope of your day-to-day operations.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Provide multiple channels for notification (email, Instant Messages, pager text, etc.)<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Users should be able (and encouraged) to update, document, and share the information needed to start troubleshooting.<\/span><\/p>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Keep Them Informed<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">Users often need to use monitoring data for further analysis, or for reports. The monitoring application itself should assist, with built-in reporting tools. Performance statistics and an overall summary should be generated at least once a week. Analysis of critical or noteworthy events should be available, on a daily basis.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Allow users to capture and save monitoring data \u2013 e.g., the \u201cnormal\u201d performance figures used as a baseline for troubleshooting. Users should be able to easily specify what they want recorded (variables, format, duration, etc.). They should also be allowed to log the information they\u2019re monitoring.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">There should be a central repository, for all logs from different areas of monitoring. A single UI can then be used, to analyze the data. Export tools (to formats such as .xls, .html, .txt, .csv) should be provided. This will help to facilitate collaboration in reporting and troubleshooting.<\/span><\/p>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Take Appropriate Measures<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">Different graph types should be appropriate to the type of information you are analyzing.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Line graphs are good for displaying one or more variables on a scale, such as time. Ranges, medians, and means can all be shown simultaneously.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Table format makes it easy for users to see precise numbers. Table cells can also contain graphical elements associated with numbers, or symbols to indicate state. The most important information should appear first, or highlighted so that it can be taken in at glance.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Histograms or bar graphs allow values at a single point in time to be compared easily. Ranges, medians, and means can all be displayed simultaneously.<\/span><\/p>\n<h3><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Some recommendations:<\/strong><\/span><\/h3>\n<ul>\n<li><span style=\"font-family: verdana,geneva;\">When using a line graph, show as few variables as possible. Five is a safe maximum. This makes the graph easier to read<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Avoid using stacked bar graphs. It\u2019s better to use a histogram, and put the values in clusters along the same baseline. Alternatively, break them up into separate graphs<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">When using a graph to show percentage data, always use a pie chart<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Consider providing a details pane; clicking a graph will display details about the graph in the pane<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Avoid trying to convey too many messages in one graph<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Never use a graph to display a single data point (a single number)<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Avoid the use of 3D in your charts; it can be distracting<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">Allow users to easily flip between different views of the same data<\/span><\/li>\n<\/ul>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Push the Relevant Facts<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">Displaying a lot of stuff onscreen makes it harder for administrators to spot the information that is of most value \u2013 like critical error messages.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Draw attention to what needs attention, most:<\/span><\/p>\n<ul>\n<li><span style=\"font-family: verdana,geneva;\">by placing important items prominently<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">by putting more important information before the less important<\/span><\/li>\n<li><span style=\"font-family: verdana,geneva;\">by using visual signposts, such as text or an icon, to indicate important information<\/span><\/li>\n<\/ul>\n<p><span style=\"font-family: verdana,geneva;\">Preconfigured monitoring views will reduce the emphasis on users configuring the system. Allow users to customise the information and highlight what they think is important, so it can be elevated in the UI. Group similar events \u2013 and consider having a global overview of the system, visible at all times.<\/span><\/p>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Hide the Redundant<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">If it hasn\u2019t gone critical, or isn\u2019t affecting anything, they don\u2019t need to see it. At least, not immediately. If a failure reoccurs, don\u2019t keep showing the same event, over and over. Try to group similar events into one.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Allow your users to tag certain events as ones they don\u2019t want to view. Let them set thresholds that match their own monitoring criteria. This allows them to create environment-specific standards, and reduces false alarms. Use filters and views, to give users granular control of what they are monitoring.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Provide the ability to zoom in for more detailed information, or zoom out for aggregated data. Allow users to hide unimportant events, but still have them accessible.<\/span><\/p>\n<h2><span style=\"color: #ff6600; font-family: verdana,geneva;\"><strong>Be Prepared, for the Worst<\/strong><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">As well as probable causes, the application should suggest possible solutions, for any problems that occur. Administrators will likely have preferred methods of troubleshooting. But, in diagnostic sciences, it helps to get a second opinion. It\u2019s essential to identify events most indicative of potential operational or security issues. Then, automate the creation of alerts on those events, to notify the appropriate personnel.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Being prepared also means that all data should be backed up and stored off the premises as well as on the network. This protects against the obvious such as hardware failure or malware attacks, but also against complete disaster such as a fire at the premises.<\/span><\/p>\n<h2><span style=\"font-family: verdana,geneva;\"><iframe loading=\"lazy\" src=\"\/\/embed.gettyimages.com\/embed\/459223411?et=H7wTS-ffsU28fZUzZNNqKg&amp;sig=EaUH_W90aNgv7LNbKAGVsCIQh-UwmOkpAcAl3IFtFBE=\" width=\"250\" height=\"224\" frameborder=\"0\" scrolling=\"no\" align=\"right\"><\/iframe><span style=\"color: #ff6600;\"><strong>And the Best, that Can Happen<\/strong><\/span><\/span><\/h2>\n<p><span style=\"font-family: verdana,geneva;\">With proper monitoring measures in place, you greatly reduce the risk<\/span><br>\n<span style=\"font-family: verdana,geneva;\"> of losses due to poor server performance. This has a corresponding positive effect on your business \u2013 especially online services and transactions.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">A well-tuned monitoring system will help facilitate the identification of potential issues, and accelerate the process of fixing unexpected problems before they can affect your users.<\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\"> <\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\"> <\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\"><a title=\"\" href=\"http:\/\/www.twitter.com\/home?status=RT:%20@poweradmn%20DFS%20in%20a%20Windows%20Server%20Infrastructure%20and%20DFS%20Replication%20\/blog\/dfs-in-a-windows-server-infrastructure-dfs-replication\/?ref=blog\" target=\"_blank\" rel=\"nofollow\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-medium wp-image-1028\" title=\"Tweet this\" src=\"\/blog\/wp-content\/uploads\/2013\/11\/tweet-this-article-button-large-300x75.png\" alt=\"Tweet this\" width=\"300\" height=\"75\" srcset=\"https:\/\/www.poweradmin.com\/blog\/wp-content\/uploads\/2013\/11\/tweet-this-article-button-large-300x75.png 300w, https:\/\/www.poweradmin.com\/blog\/wp-content\/uploads\/2013\/11\/tweet-this-article-button-large.png 310w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\"><img class=\"extlink-icon\" src=\"https:\/\/www.poweradmin.com\/blog\/wp-content\/plugins\/external-links-nofollow-open-in-new-tab-favicon\/images\/extlink.png\"><\/a><\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\"><a title=\"\" href=\"https:\/\/plus.google.com\/share?url={\/blog\/dfs-in-a-windows-server-infrastructure-dfs-replication\/?ref=blog}\" target=\"_blank\" rel=\"nofollow\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-medium wp-image-1053\" title=\"Share on Google+\" src=\"\/blog\/wp-content\/uploads\/2013\/11\/google-plus-this-article-button-large2-300x75.png\" alt=\"Share on Google+\" width=\"300\" height=\"75\" srcset=\"https:\/\/www.poweradmin.com\/blog\/wp-content\/uploads\/2013\/11\/google-plus-this-article-button-large2-300x75.png 300w, https:\/\/www.poweradmin.com\/blog\/wp-content\/uploads\/2013\/11\/google-plus-this-article-button-large2.png 310w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\"><img class=\"extlink-icon\" src=\"https:\/\/www.poweradmin.com\/blog\/wp-content\/plugins\/external-links-nofollow-open-in-new-tab-favicon\/images\/extlink.png\"><\/a><\/span><\/p>\n<p><span style=\"font-family: verdana,geneva;\">Photo Credit: <a href=\"http:\/\/www.flickr.com\/photos\/40491122@N03\/3738306829\/\" rel=\"nofollow\" target=\"_blank\">PrepareToWed<img class=\"extlink-icon\" src=\"https:\/\/www.poweradmin.com\/blog\/wp-content\/plugins\/external-links-nofollow-open-in-new-tab-favicon\/images\/extlink.png\"><\/a> via <a href=\"http:\/\/compfight.com\" rel=\"nofollow\" target=\"_blank\">Compfight<img class=\"extlink-icon\" src=\"https:\/\/www.poweradmin.com\/blog\/wp-content\/plugins\/external-links-nofollow-open-in-new-tab-favicon\/images\/extlink.png\"><\/a> <a href=\"http:\/\/www.flickr.com\/help\/general\/#147\">cc<\/a><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>As a business, you may be running many on-site or Web-based applications and services. Security, data handling, transaction support, load balancing, or the management of large distributed systems. The deployment of these will depend on the condition of your servers. So it\u2019s vital for you to continuously monitor their health and performance. Here are some [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":1685,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,10,9,8],"tags":[],"class_list":["post-1518","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general-it","category-how-to","category-power-admin","category-technical","category-windows"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/1518","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/comments?post=1518"}],"version-history":[{"count":5,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/1518\/revisions"}],"predecessor-version":[{"id":3529,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/1518\/revisions\/3529"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media\/1685"}],"wp:attachment":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media?parent=1518"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/categories?post=1518"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/tags?post=1518"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}