Skip to main content

Tengine monitoring with Netdata

Tengine is a web server originated by Taobao, the largest e-commerce website in Asia. It is based on the Nginx HTTP server and has many advanced features.

This module monitors one or more Tengine instances, depending on your configuration.

Requirements#

Charts#

It produces the following summary charts:

  • Bandwidth in B/s
  • Connections in connections/s
  • Requests in requests/s
  • Requests Per Response Code Family in requests/s
  • Requests Per Response Code Detailed in requests/s
  • Number Of Requests Calling For Upstream in requests/s
  • Number Of Times Calling For Upstream in calls/s
  • Requests Per Response Code Family in requests/s

Configuration#

Edit the go.d/tengine.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/tengine.conf

Needs only url to server's /us. Here is an example for 2 servers:

jobs:
- name: local
url: http://127.0.0.1/us
- name: remote
url: http://203.0.113.10/us

For all available options please see module configuration file.

Troubleshooting#

To troubleshoot issues with the tengine collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

First, navigate to your plugins directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the setting plugins directory. Once you're in the plugin's directory, switch to the netdata user.

cd /usr/libexec/netdata/plugins.d/
sudo -u netdata -s

You can now run the go.d.plugin to debug the collector:

./go.d.plugin -d -m tengine

Reach out

If you need help after reading this doc, search our community forum for an answer. There's a good chance someone else has already found a solution to the same issue.

Documentation

Community

Last updated on