[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-10380":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":15,"stars30d":16,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":17,"rankGlobal":9,"rankLanguage":9,"license":18,"archived":19,"fork":19,"defaultBranch":20,"hasWiki":21,"hasPages":19,"topics":22,"createdAt":9,"pushedAt":9,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":15,"starSnapshotCount":15,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},10380,"ngxtop","lebinh\u002Fngxtop","lebinh","Real-time metrics for nginx server",null,"Python",6526,474,202,47,0,1,64.13,"MIT License",false,"master",true,[23,24,25],"cli","monitoring","nginx","2026-06-12 04:00:50","================================================================\n``ngxtop`` - **real-time** metrics for nginx server (and others)\n================================================================\n\n**ngxtop** parses your nginx access log and outputs useful, ``top``-like, metrics of your nginx server.\nSo you can tell what is happening with your server in real-time.\n\n    ``ngxtop`` is designed to run in a short-period time just like the ``top`` command for troubleshooting and monitoring\n    your Nginx server at the moment. If you need a long running monitoring process or storing your webserver stats in external\n    monitoring \u002F graphing system, you can try `Luameter \u003Chttps:\u002F\u002Fluameter.com>`_.\n\n``ngxtop`` tries to determine the correct location and format of nginx access log file by default, so you can just run\n``ngxtop`` and having a close look at all requests coming to your nginx server. But it does not limit you to nginx\nand the default top view. ``ngxtop`` is flexible enough for you to configure and change most of its behaviours.\nYou can query for different things, specify your log and format, even parse remote Apache common access log with ease.\nSee sample usages below for some ideas about what you can do with it.\n\nInstallation\n------------\n\n::\n\n    pip install ngxtop\n\n\nNote: ``ngxtop`` is primarily developed and tested with python2 but also supports python3.\n\nUsage\n-----\n\n::\n\n    Usage:\n        ngxtop [options]\n        ngxtop [options] (print|top|avg|sum) \u003Cvar>\n        ngxtop info\n\n    Options:\n        -l \u003Cfile>, --access-log \u003Cfile>  access log file to parse.\n        -f \u003Cformat>, --log-format \u003Cformat>  log format as specify in log_format directive.\n        --no-follow  ngxtop default behavior is to ignore current lines in log\n                         and only watch for new lines as they are written to the access log.\n                         Use this flag to tell ngxtop to process the current content of the access log instead.\n        -t \u003Cseconds>, --interval \u003Cseconds>  report interval when running in follow mode [default: 2.0]\n\n        -g \u003Cvar>, --group-by \u003Cvar>  group by variable [default: request_path]\n        -w \u003Cvar>, --having \u003Cexpr>  having clause [default: 1]\n        -o \u003Cvar>, --order-by \u003Cvar>  order of output for default query [default: count]\n        -n \u003Cnumber>, --limit \u003Cnumber>  limit the number of records included in report for top command [default: 10]\n        -a \u003Cexp> ..., --a \u003Cexp> ...  add exp (must be aggregation exp: sum, avg, min, max, etc.) into output\n\n        -v, --verbose  more verbose output\n        -d, --debug  print every line and parsed record\n        -h, --help  print this help message.\n        --version  print version information.\n\n        Advanced \u002F experimental options:\n        -c \u003Cfile>, --config \u003Cfile>  allow ngxtop to parse nginx config file for log format and location.\n        -i \u003Cfilter-expression>, --filter \u003Cfilter-expression>  filter in, records satisfied given expression are processed.\n        -p \u003Cfilter-expression>, --pre-filter \u003Cfilter-expression> in-filter expression to check in pre-parsing phase.\n        \n        Supported log formats: combined (default), common, caddy (for Caddy JSON access logs)\n\nSamples\n-------\n\nDefault output\n~~~~~~~~~~~~~~\n\n::\n\n    $ ngxtop\n    running for 411 seconds, 64332 records processed: 156.60 req\u002Fsec\n\n    Summary:\n    |   count |   avg_bytes_sent |   2xx |   3xx |   4xx |   5xx |\n    |---------+------------------+-------+-------+-------+-------|\n    |   64332 |         2775.251 | 61262 |  2994 |    71 |     5 |\n\n    Detailed:\n    | request_path                             |   count |   avg_bytes_sent |   2xx |   3xx |   4xx |   5xx |\n    |------------------------------------------+---------+------------------+-------+-------+-------+-------|\n    | \u002Fabc\u002Fxyz\u002Fxxxx                            |   20946 |          434.693 | 20935 |     0 |    11 |     0 |\n    | \u002Fxxxxx.json                              |    5633 |         1483.723 |  5633 |     0 |     0 |     0 |\n    | \u002Fxxxxx\u002Fxxx\u002Fxxxxxxxxxxxxx                 |    3629 |         6835.499 |  3626 |     0 |     3 |     0 |\n    | \u002Fxxxxx\u002Fxxx\u002Fxxxxxxxx                      |    3627 |        15971.885 |  3623 |     0 |     4 |     0 |\n    | \u002Fxxxxx\u002Fxxx\u002Fxxxxxxx                       |    3624 |         7830.236 |  3621 |     0 |     3 |     0 |\n    | \u002Fstatic\u002Fjs\u002Fminified\u002Futils.min.js         |    3031 |         1781.155 |  2104 |   927 |     0 |     0 |\n    | \u002Fstatic\u002Fjs\u002Fminified\u002Fxxxxxxx.min.v1.js    |    2889 |         2210.235 |  2068 |   821 |     0 |     0 |\n    | \u002Fstatic\u002Ftracking\u002Fjs\u002Fxxxxxxxx.js          |    2594 |         1325.681 |  1927 |   667 |     0 |     0 |\n    | \u002Fxxxxx\u002Fxxx.html                          |    2521 |          573.597 |  2520 |     0 |     1 |     0 |\n    | \u002Fxxxxx\u002Fxxxx.json                         |    1840 |          800.542 |  1839 |     0 |     1 |     0 |\n\nView top source IPs of clients\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n::\n\n    $ ngxtop top remote_addr\n    running for 20 seconds, 3215 records processed: 159.62 req\u002Fsec\n\n    top remote_addr\n    | remote_addr     |   count |\n    |-----------------+---------|\n    | 118.173.177.161 |      20 |\n    | 110.78.145.3    |      16 |\n    | 171.7.153.7     |      16 |\n    | 180.183.67.155  |      16 |\n    | 183.89.65.9     |      16 |\n    | 202.28.182.5    |      16 |\n    | 1.47.170.12     |      15 |\n    | 119.46.184.2    |      15 |\n    | 125.26.135.219  |      15 |\n    | 125.26.213.203  |      15 |\n\nList 4xx or 5xx responses together with HTTP referer\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n::\n\n    $ ngxtop -i 'status >= 400' print request status http_referer\n    running for 2 seconds, 28 records processed: 13.95 req\u002Fsec\n\n    request, status, http_referer:\n    | request   |   status | http_referer   |\n    |-----------+----------+----------------|\n    | -         |      400 | -              |\n\nParse apache log from remote server with `common` format\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n::\n\n    $ ssh user@remote_server tail -f \u002Fvar\u002Flog\u002Fapache2\u002Faccess.log | ngxtop -f common\n    running for 20 seconds, 1068 records processed: 53.01 req\u002Fsec\n\n    Summary:\n    |   count |   avg_bytes_sent |   2xx |   3xx |   4xx |   5xx |\n    |---------+------------------+-------+-------+-------+-------|\n    |    1068 |        28026.763 |  1029 |    20 |    19 |     0 |\n\n    Detailed:\n    | request_path                             |   count |   avg_bytes_sent |   2xx |   3xx |   4xx |   5xx |\n    |------------------------------------------+---------+------------------+-------+-------+-------+-------|\n    | \u002Fxxxxxxxxxx                              |     199 |        55150.402 |   199 |     0 |     0 |     0 |\n    | \u002Fxxxxxxxx\u002Fxxxxx                          |     167 |        47591.826 |   167 |     0 |     0 |     0 |\n    | \u002Fxxxxxxxxxxxxx\u002Fxxxxxx                    |      25 |         7432.200 |    25 |     0 |     0 |     0 |\n    | \u002Fxxxx\u002Fxxxxx\u002Fx\u002Fxxxxxxxxxxxxx\u002Fxxxxxxx      |      22 |          698.727 |    22 |     0 |     0 |     0 |\n    | \u002Fxxxx\u002Fxxxxx\u002Fx\u002Fxxxxxxxxxxxxx\u002Fxxxxxx       |      19 |         7431.632 |    19 |     0 |     0 |     0 |\n    | \u002Fxxxxx\u002Fxxxxx\u002F                            |      18 |         7840.889 |    18 |     0 |     0 |     0 |\n    | \u002Fxxxxxxxx\u002Fxxxxxxxxxxxxxxxxx              |      15 |         7356.000 |    15 |     0 |     0 |     0 |\n    | \u002Fxxxxxxxxxxx\u002Fxxxxxxxx                    |      15 |         9978.800 |    15 |     0 |     0 |     0 |\n    | \u002Fxxxxx\u002F                                  |      14 |            0.000 |     0 |    14 |     0 |     0 |\n    | \u002Fxxxxxxxxxx\u002Fxxxxxxxx\u002Fxxxxx               |      13 |        20530.154 |    13 |     0 |     0 |     0 |\n\nParse Caddy server access log with JSON format\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n::\n\n    $ ngxtop -l \u002Fvar\u002Flog\u002Fcaddy\u002Faccess.log -f caddy\n    running for 15 seconds, 234 records processed: 15.60 req\u002Fsec\n\n    Summary:\n    |   count |   avg_bytes_sent |   2xx |   3xx |   4xx |   5xx |\n    |---------+------------------+-------+-------+-------+-------|\n    |     234 |         5482.342 |   198 |    12 |    22 |     2 |\n\n    Detailed:\n    | request_path                        |   count |   avg_bytes_sent |   2xx |   3xx |   4xx |   5xx |\n    |-------------------------------------+---------+------------------+-------+-------+-------+-------|\n    | \u002Fapi\u002Fv1\u002Fusers                       |      32 |          128.000 |    32 |     0 |     0 |     0 |\n    | \u002Fimages\u002Flogo.png                    |      28 |        24560.000 |    28 |     0 |     0 |     0 |\n    | \u002Fblog\u002Farticle-not-found             |      22 |         5621.000 |     0 |     0 |    22 |     0 |\n    | \u002Faudiobooks                         |      21 |        16818.000 |    21 |     0 |     0 |     0 |\n    | \u002Fv1\u002Fsessions\u002F12345                  |      18 |           35.000 |    18 |     0 |     0 |     0 |\n    | \u002Fstatic\u002Fcss\u002Fmain.css                |      17 |         1459.000 |    17 |     0 |     0 |     0 |\n    | \u002Fstatic\u002Fjs\u002Fapp.js                   |      15 |         5824.000 |    15 |     0 |     0 |     0 |\n    | \u002F                                   |      12 |         3245.000 |     0 |    12 |     0 |     0 |\n    | \u002Fapi\u002Fv2\u002Fmetrics                     |      10 |          873.000 |     8 |     0 |     0 |     2 |\n    | \u002Ffavicon.ico                        |       8 |         1246.000 |     8 |     0 |     0 |     0 |\n\nGroup by host (useful in multi-host setups)\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n::\n\n    $ ngxtop -l \u002Fvar\u002Flog\u002Fcaddy\u002Faccess.log -f caddy --group-by host\n    running for 10 seconds, 156 records processed: 15.60 req\u002Fsec\n\n    Summary:\n    |   count |   avg_bytes_sent |   2xx |   3xx |   4xx |   5xx |\n    |---------+------------------+-------+-------+-------+-------|\n    |     156 |         7281.632 |   142 |     8 |     4 |     2 |\n\n    Detailed:\n    | host                |   count |   avg_bytes_sent |   2xx |   3xx |   4xx |   5xx |\n    |---------------------+---------+------------------+-------+-------+-------+-------|\n    | api.example.com     |      75 |          124.533 |    73 |     0 |     0 |     2 |\n    | static.example.net  |      42 |        16903.857 |    42 |     0 |     0 |     0 |\n    | example.org         |      31 |         3791.258 |    19 |     8 |     4 |     0 |\n    | imusic.br.com       |       8 |        16818.000 |     8 |     0 |     0 |     0 |\n\n","ngxtop 是一个用于实时监控 Nginx 服务器的工具。它通过解析 Nginx 的访问日志，提供类似于 top 命令的实时指标，帮助用户了解服务器当前的状态。该工具支持自定义日志格式和位置，并且可以处理远程 Apache 日志，具有很高的灵活性。此外，ngxtop 还允许用户根据需要配置查询、分组及排序等行为，以满足不同的监控需求。适用于需要即时查看 Nginx 服务器性能或进行故障排查的场景，但不建议作为长期运行的监控解决方案使用。",2,"2026-06-11 03:28:05","top_topic"]