Difference between revisions of "Server Status"

From meteoplug
Jump to: navigation, search
(Created page with "<iframe key="meteoplug" path="cgi-bin/meteochart.cgi?draw=7c7e7d7b7976323b3f3620267a2b2c74382c2424302221372276212720282a height="820" width="730" /> Please notice, time is gi...")
 
Line 1: Line 1:
<iframe key="meteoplug" path="cgi-bin/meteochart.cgi?draw=7c7e7d7b7976323b3f3620267a2b2c74382c2424302221372276212720282a height="820" width="730" />
+
<iframe key="meteoplug" path="cgi-bin/meteochart.cgi?draw=7c7e7d7b7976323b3f3620267a2b2c74382c2424302221372276212720282a" height="820" width="730" />
  
 
Please notice, time is given in UTC (GMT). Depending on your geographical location your local time will differ from that. If you are interested, the chart above does give some usefull information about the Meteoplug server status. You can read the chart as follows:
 
Please notice, time is given in UTC (GMT). Depending on your geographical location your local time will differ from that. If you are interested, the chart above does give some usefull information about the Meteoplug server status. You can read the chart as follows:

Revision as of 16:28, 9 February 2020

Please notice, time is given in UTC (GMT). Depending on your geographical location your local time will differ from that. If you are interested, the chart above does give some usefull information about the Meteoplug server status. You can read the chart as follows:

  • Processes shows the number of processes running on the server. The number is not very interesting as such, but when you see this number increasing, the server faces additional tasks.
  • System Load is given in percent. 100% says that a one core machine is running at optimal load. The server has 4 cores and multithreading, therefore, loads up to 600% should be ok. However, seeing system load going up also indicates that the server is taking additional or tougher jobs.
  • Import Queue tells you how many stations do have data transferred to the server not been imported to the database yet. When the system is under heavy load this number will increase. When the server can handle all import requests in real time, this number is below 10. Queued data will not be available for charting, weather networks, etc.
  • Recompute Queue tells you how many issued recomputation jobs are in the queue. Recomputation of a multi year data set of a Meteoplug client can take a few hours and will be done in parallel to normal operation. So please be patient. Your web interface also tells you, if you have a job running and/or jobs in the queue.
  • Import Age measures the age of the oldest non-processed data import request. This is an indicator how long it will take until sent data will appear in graphs, etc.
  • Live Data Queue indicates how many data records from live data sending stations are in the queue for computation. This queue should stay reasonable short and should not continue to grow as live data does not like to be queued up.
  • Live Data Age tells you the age of the oldest not processed live data record in seconds. If this goes beyond a very few seconds data is at risk no longer being regarded as "live".
  • Throughput per second informs about the current throughput of the live data processing engine. It is a statistically number and does not mean that such many records have been processed last second, but current system parameters indicate that the engine can take such a load.
  • Live Stations displays the number of stations reporting live data to Meteoplug.
  • Requests per minute informs how many live data display requests have been received by the server.
  • Submission per minute tells how many data submission from station uploading live data have been received during the last minute.

Chart below gives some additional info about physical server status, which might be an indication of overall system health.