Nginx Nginx Amplify Open Source Monitoring Service

yeah the nginx insight is nice

nginx have announced custom dashboards for Amplify too Introducing Custom Dashboards in NGINX Amplify - NGINX

 

Nginx Amplify has gone public beta now Announcing the Public Beta Release of NGINX Amplify - NGINX

I had to update my amplify agent via yum

Code (Text):

yum update nginx-amplify-agent --disableplugin=priorities --disableexcludes=main

 

alerts are new right.. i set them up a while ago

custom dashboards seem a bit confusing. I suggest that you also have a few pre-made custom dashboard templates that folks can create from to start with

 

FYI, just updated Centmin Mod 123.09beta01 and switched to a new custom nginx log_format which supports Nginx Amplify's additional metrics Beta Branch - switch nginx access_log to custom main_ext format by default 123.09beta01 | Centmin Mod Community

 

what Centmin Mod Nginx's new format for Nginx Amplify metrics ? seems logstalgia supports nginx log format Logstalgia - a website access log visualization tool but not 100% sure as never used logstalgia and no idea for unicode

if new log_format i added to Centmin Mod's Nginx doesn't work, just change and revert the vhost conf file to use combined instead main_ext log_format

 

Time to update Nginx GPG Keys Nginx - Updating GPG Keys for Nginx products | Centmin Mod Community

 

wow 1 1/2 yrs later and Nginx Amplify still needs the workaround listed at https://community.centminmod.com/th...en-source-monitoring-service.4963/#post-20812 to install on Centmin Mod LEMP stack servers due to nginx being excluded from yum.conf.

I posted the small change you need to make in install.sh on line 412 at https://gist.github.com/centminmod/90da4ed19b94524e6fd8dc23fe31fe1f/revisions to change the line to

Code (Text):

install_cmd="yum ${assume_yes} install --disableexcludes=main"

so simple to fix in install.sh just add a check to make sure nginx isn't listed in /etc/yum.conf exclude line

Code (Text):

grep -w nginx /etc/yum.conf
exclude=*.i386 *.i586 *.i686 nginx* php* mysql*

Code (Text):

if [[ "$(grep -w nginx /etc/yum.conf)" ]]; then
  install_cmd="yum ${assume_yes} install --disableexcludes=main"
else
  install_cmd="yum ${assume_yes} install"
fi

submitted to issue tracker https://github.com/nginxinc/nginx-amplify-agent/issues/52

 

sort of they added detection for nginx exclude and prompt user if they want to disable nginx exclusion to install nginx amplify instead of automatically disabling nginx exclusion workaround fix for nginx exclude by centminmod · Pull Request #53 · nginxinc/nginx-amplify-agent · GitHub

 

yup

 

nginx stub status is configured by default in main hostname's vhost config file at /usr/local/nginx/conf/conf.d/virtual.conf

Code (Text):

        location /nginx_status {
        stub_status on;
        #access_log   off;
        allow 127.0.0.1;
        #allow youripaddress;
        deny all;
        }

as per nginx-amplify-doc/amplify-guide.md at master · nginxinc/nginx-amplify-doc · GitHub

and see nginx-amplify-doc/amplify-guide.md at master · nginxinc/nginx-amplify-doc · GitHub

additional metrics need changing log format nginx-amplify-doc/amplify-guide.md at master · nginxinc/nginx-amplify-doc · GitHub which centmin mod 123.09beta01 did do for some time but reverted to default for fail2ban support which probably is more important to have

You can setup 2 separate access logs one for nginx default format + one for amplify advanced metrics but need extra work

nginx-amplify-doc/amplify-guide.md at master · nginxinc/nginx-amplify-doc · GitHub

So I guess for 123.09beta01 only it would mean something like this in vhosts' config files

Code (Text):

access_log /home/nginx/domains/domain.com/log/access.log combined buffer=256k flush=5m;
access_log /home/nginx/domains/domain.com/log/access-amplify.log main_ext;

thus leaving default combined log format for nginx for access.log and using new separate log for access-amplify.log with main_ext log format that 123.09beta01 has support for in nginx.conf that I added when Nginx amplify first came out

Code (Text):

log_format  main  '$remote_addr - $remote_user [$time_local] $request '
                '"$status" $body_bytes_sent "$http_referer" '
                '"$http_user_agent" "$http_x_forwarded_for" "$gzip_ratio"'
                ' "$connection" "$connection_requests" "$request_time"';

log_format  ddos-proxy '$remote_addr for $http_x_real_ip - $remote_user [$time_local] $request '
                '"$status" $body_bytes_sent "$http_referer" '
                '"$http_user_agent" "$http_x_forwarded_for" "$gzip_ratio"'
                ' "$connection" "$connection_requests" "$request_time"';

log_format  main_ext '$remote_addr - $remote_user [$time_local] "$request" '
                         '$status $body_bytes_sent "$http_referer" '
                         '"$http_user_agent" "$http_x_forwarded_for" '
                         'rt=$request_time ua="$upstream_addr" '
                         'us="$upstream_status" ut="$upstream_response_time" '
                         'ul="$upstream_response_length" '
                         'cs=$upstream_cache_status' ;

then in /etc/amplify-agent/agent.conf

Code (Text):

[nginx]
exclude_logs=/home/nginx/domains/*/log/access.log

you'd have to setup a separate access log file for every nginx vhost on your server for this to work

Code (Text):

access_log /home/nginx/domains/domain.com/log/access.log combined buffer=256k flush=5m;
access_log /home/nginx/domains/domain.com/log/access-amplify.log main_ext;

otherwise, the agent.conf exclude_logs will exclude all vhost's access.log unless you change the exclude_logs entry for only specific web host you want to exclude i.e.
in /etc/amplify-agent/agent.conf

Code (Text):

[nginx]
exclude_logs=/home/nginx/domains/onlydomain.com/log/access.log