![]() |
|
With the Internet being adopted as a primary medium of exposure, Web site up time, known as Quality of Service (QoS), is critical. Web sites can go down for a variety of reasons both internal (for example, memory leaks, malfunctioning of a program) and external (for example, virus, DoS attacks).
Pramati Server Management Console provides a feature to monitor response time for a Web site periodically. QoS monitoring is configured in qos-config.xml.
The parameters are set by editing qos-config.xml located at . The body of the XML is initially commented. To enable QoS, uncomment it and restart the Server if it’s already running. Here is an example:
<qos-config>
<configuration-entity>
<url-entry url="http://localhost:8181/admin/index.jsp" isSecure="true" user="root" password="BASE 64 ENCODED PASSWORD">
<ping-interval-secs>20</ping-interval-secs>
<number-of-attempts>2</number-of-attempts>
<response-timeout-secs>10</response-timeout-secs>
</url-entry>
</configuration-entity>
</qos-config>
Table 1: Description for tags in qos-config.xml
| Tag | Description |
|---|---|
| url-entry | Enter the URL to be monitored to ascertain the up time. URLs can be hosted on any Pramati Server. If the URL is a secure resource, specify username and password. The QoS utility uses the username and password to login to the system before accessing the URL. |
| ping-interval-secs | Enter the interval after which the request is sent. |
| number-of-attempts | Enter maximum number of requests to be sent to the URL before triggering an action. |
| response-timeout-secs | Time elapsed before QoS marks the request as invalid. |
If the time interval is configured for 3600 seconds, QoS utility sends a request to the corresponding URL every hour. If the number of attempts is set to 2, QoS sends the request twice before triggering an action. If the response time is set as 5, QoS sends a request and waits for 5 seconds before considering it as invalid. If the request is invalid, QoS keeps sending requests as specified. If the all the requests are invalid, the System Administrator can take suitable action.
To apply any changes made to the XML, restart the Server.
<configuration-entity>
<url-entry url="url1" isSecure="true/false" user="" password="">
<ping-interval-secs>20</ping-interval-secs>
<number-of-attempts>2</number-of-attempts>
<response-timeout-secs>10</response-timeout-secs>
<url-entry>
<url-entry url="url2" isSecure="true/false" user="" password="">
<ping-interval-secs>20</ping-interval-secs>
<number-of-attempts>2</number-of-attempts>
<response-timeout-secs>10</response-timeout-secs>
</url-entry>
</configuration-entity>
The data collected over time can be viewed on a current, daily, weekly, monthly, and yearly basis by selecting the relevant option from the drop-down list at the bottom right corner of the graph.
Note: To view the graph in your browser, you require a Macromedia FlashTM plug-in.
| © Pramati Technologies 2007 | Runs on Pramati Server | Feedback | Legal |