Monitis is pleased to present the following tips for configuring Apache Tomcat for maximum performance. Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies. Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.
This article is the second article in our series about SharePoint. In our first article we provided a few SharePoint basic system performance counters that you can use to monitor the overall health of the server itself that is running SharePoint; a requirement before you can monitor SharePoint effectively and detect and identify possible bottlenecks. In this article we’ll discuss SharePoint monitoring more in depth and provide some best practices.
SharePoint 2010 offers a number of built-in monitoring features for diagnosing problems and performance. By default diagnostic logging is enabled and while most of the time these default settings will be sufficient, there might be times when you want to make changes to these settings. For example, if you are making a major change to your environment, you can configure a more verbose level of logging to track more closely if everything is working as planned.
Apache is the most popular webserver, and M3 (Monitis Monitor Manager) is one very powerful Monitis tool. It’s a no-brainer to bring them together.
In this short document, first we will look briefly at how Apache presents its logs. Next we will define the way to measure the speed of a webserver, and finally we will learn how we can present results with Monitis (using M3).
HTTP what?
Yes, HTTP extraction. Imagine you have a web page you would like to probe for parameters. Such as the number of your twitter subscribers, or the temperature somewhere – and profile it in Monitis.
Or another scenario could be to probe the responsiveness of your website – how fast is it?
Was it compromised and defaced?
I think you get the point – it is needed and important.
In the previous article we’ve shown how easy it is to integrate popular Nagios server monitoring commands, or plugins, with Monitis M3 monitoring framework.
However, given the fact you have a working Nagios configuration, which is vast and complex – I can sympathize with your unwillingness to actually migrate to Monitis.
Monitis provides built in functionality to monitor a wide variety of system statistics as well as the ability to create custom system monitors. Monitis Monitor Manager, or M3 for short, allows you to take these custom monitors even further by providing you with a simple framework to use the incredible power of regular expressions to pull and format literally any kind of data and automatically send it over the wire to your Monitis dashboard.
Apache and syslog-ng
While logging to a database back-end has its benefits, the setup as it stands leaves us wanting. Some applications, such as Apache, do not log via syslog-ng by default. The good news is that this can be easily remedied, and there are a couple of different ways of doing this. First, the less good way:
After the first article on syslog-ng, you should have a pretty good feel of how syslog-ng works. As you recall, the sources define what is logged, destinations determine where the logs go, and the log statements are what tells syslog-ng to create the log. However, much of the time we don’t want all of our system logs going to the same file. It can be quite useful to break up those logs in to multiple files, and to sort them by content. This is where filters come in.
Apache and MySQL make up the backbone of many Linux based web servers. According to the August 2011 Web Server Survey by Netcraft, Apache currently runs on 65.18% (or 301,771,518!) of web servers. Similarly, MySQL is the most popular open source database and holds a significant portion of the market share – especially for web content. This article will detail how you can get at the ‘low-hanging fruit’ in order to make some simple changes that will yield big performance gains.
other web servers. In fact, NGINX is now the 2nd most widely used web server (22 million websites) in the world. NGINX fanboys will tell you no one can top their love of NGINX, because it succeeds in efforts to achieve high performance with small memory footprint. It makes NGINX suitable to deliver static content, to work as a reverse proxy, or even to run as a load balancer, all of the above in a fast and scalable way. Several well-known companies pick NGINX to power their sites, including WordPress and Github.
