Tengine is an open source web server based on the popular open source web server, Nginx. It is developed and maintained by web giant Taobao. It is optimized for performance and security and supports a wide range of features such as load balancing, streaming media, and static file caching.
The prerequisites for monitoring Tengine with Netdata are to have Tengine and Netdata installed on your system.
Netdata auto discovers hundreds of services, and for those it doesn’t turning on manual discovery is a one line configuration. For more information on configuring Netdata for Tengine monitoring please read the collector documentation.
You should now see the Tengine section on the Overview tab in Netdata Cloud already populated with charts about all the metrics you care about.
Netdata has a public demo space (no login required) where you can explore different monitoring use-cases and get a feel for Netdata.
Bandwidth Total is the total number of bytes transferred from the web server to the client. Monitoring and observing this metric allows for the DevOps and SRE teams to determine the amount of bandwidth and resources that are being used for the website. This can help in determining whether the website is utilizing the resources efficiently or if there is unnecessary usage.
Connections Total is the total number of client connections that the web server has accepted. Monitoring and observing this metric allows for the DevOps and SRE teams to determine the amount of concurrent connections that are being handled by the web server. This can help in determining whether the website can handle the load or if there needs to be more resources allocated to the web server.
Requests Total is the total number of requests that the web server has processed. Monitoring and observing this metric allows for the DevOps and SRE teams to determine the total number of requests that the web server is handling. This can help in determining whether the website is performing efficiently or if there needs to be an increase in resources allocated to the web server.
Requests Per Response Code Family Total is the total number of requests that the web server has responded to in each response code family (2xx, 3xx, 4xx, 5xx and other). Monitoring and observing this metric allows for the DevOps and SRE teams to determine the number of requests that are being responded to with each response code family. This can help in determining whether the website is responding to requests efficiently and successfully or if there is an issue with the responses. Normal value ranges for Requests Per Response Code Family Total should be balanced, with more requests being responded to successfully with 2xx and 3xx codes and fewer requests being responded to with 4xx and 5xx codes.
Requests Per Response Code Detailed Total is the total number of requests that the web server has responded to in each detailed response code (200, 206, 302, 304, 403, 404, 419, 499, 500, 502, 503, 504, 508 and other). Monitoring and observing this metric allows for the DevOps and SRE teams to determine the number of requests that are being responded to with each detailed response code. This can help in determining whether the website is responding to requests efficiently and successfully or if there is an issue with the responses. Normal value ranges for Requests Per Response Code Detailed Total should be balanced, with more requests being responded to successfully with 200, 206, 302 and 304 codes and fewer requests being responded to with 403, 404, 419, 499, 500, 502, 503, 504 and 508 codes.
Requests Upstream Total is the total number of requests that the web server has sent to an upstream server. Monitoring and observing this metric allows for the DevOps and SRE teams to determine the amount of requests that the web server is sending to the upstream server. This can help in determining whether the web server is able to handle the requests or if there needs to be more resources allocated to the web server.
Tries Upstream Total is the total number of attempts that the web server has made to send a request to an upstream server. Monitoring and observing this metric allows for the DevOps and SRE teams to determine how many attempts the web server is making to send a request to the upstream server. This can help in determining whether the web server is able to send requests successfully or if there is an issue with the requests.
Requests Upstream Per Response Code Family Total is the total number of requests that the web server has sent to an upstream server in each response code family (4xx, 5xx). Monitoring and observing this metric allows for the DevOps and SRE teams to determine the number of requests that are being responded to with each response code family. This can help in determining whether the website is able to send requests successfully or if there is an issue with the requests. Normal value ranges for Requests Upstream Per Response Code Family Total should be balanced, with more requests being responded to successfully with 4xx codes and fewer requests being responded to with 5xx codes.
Want a personalised demo of Netdata for your use case?