Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-i argument does not filter in some cases #53

Open
max-l opened this issue Jun 12, 2015 · 1 comment
Open

-i argument does not filter in some cases #53

max-l opened this issue Jun 12, 2015 · 1 comment

Comments

@max-l
Copy link

max-l commented Jun 12, 2015

I run this :

ngxtop --no-follow -i 'upstream_response_time >=2' print upstream_response_time request

and all rows are returned. the -i filter has no effect.

nginx configuration file:
  /etc/nginx/nginx.conf
access log file:
  /var/log/nginx-access.log
access log format:
  $remote_addr [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" $request_time $upstream_response_time $pipe
available variables:
  body_bytes_sent, http_referer, http_user_agent, pipe, remote_addr, request, request_time, status, time_local, upstream_response_time
@max-l max-l changed the title -i argument does not seem to filter in some cases -i argument does not filter in some cases Jun 12, 2015
@rostagnolisandro
Copy link

Oh, what a bummer to see that this issue is still opened. I've just noticed the same: I'm not able to filter by "request_time" or "upstream_response_time". I'll take a look at the code to see if I can fix it, but I can't promise anything :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants