{"id":18747,"date":"2017-09-08T00:55:30","date_gmt":"2017-09-07T15:55:30","guid":{"rendered":"https:\/\/jirak.net\/wp\/announcing-general-availability-of-nginx-amplify\/"},"modified":"2017-09-08T01:34:57","modified_gmt":"2017-09-07T16:34:57","slug":"announcing-general-availability-of-nginx-amplify","status":"publish","type":"post","link":"https:\/\/jirak.net\/wp\/announcing-general-availability-of-nginx-amplify\/","title":{"rendered":"Announcing General Availability of NGINX Amplify"},"content":{"rendered":"<p>Announcing General Availability of NGINX Amplify<br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/jirak.net\/wp\/wp-content\/uploads\/2017\/09\/Amplify-main-diagram-964x648@2x.png\" width=\"964\" height=\"648\"><\/p>\n<p>Have you been using NGINX, but still don\u2019t have real insights into its performance? Ever wonder whether a configuration snippet copied from somewhere is a valid one? Did you ever have issues with SSL configuration in NGINX? Do you want to make NGINX run even better? Or maybe you\u2019ve just been looking around for the simplest and quickest way to set up cloud monitoring for your LEMP stack? (Where the \u201cE\u201d in &#8220;LEMP&#8221; stems from \u201ceNGINe&#8209;X\u201d ?)<\/p>\n<p>A little over a year ago, we <a href=\"https:\/\/www.nginx.com\/blog\/nginx-amplify-public-beta\/\">announced<\/a> the public beta of <a target=\"_blank\" href=\"https:\/\/amplify.nginx.com\">NGINX Amplify<\/a>&nbsp;&ndash; our own specialized, free monitoring tool for <a target=\"_blank\" href=\"https:\/\/nginx.org\/en\/\">NGINX<\/a> and <a href=\"https:\/\/nginx.com\/products\/nginx\">NGINX&nbsp;Plus<\/a>.<\/p>\n<p>Today, we\u2019re super excited to be removing the beta status for Amplify&nbsp;&ndash; it\u2019s now generally available (GA) for NGINX and NGINX&nbsp;Plus users. Amplify is production&#8209;ready, supported, and has a free&#8209;tier monitoring plan. Existing beta users&nbsp;&ndash; anyone who signed up prior to today&nbsp;&ndash; will have no interruption, and all data will be preserved. Existing features in the free&#8209;tier plan will continue to be provided at no charge. New users will have up to five free hosts to monitor with Amplify.<\/p>\n<p>It\u2019s 2017, and there are plenty of monitoring options out there, ranging from general&#8209;purpose APM product suites to the most esoteric infrastructure monitoring tools. Some of these solutions are free, open source, and do&#8209;it&#8209;yourself. Some are paid, and a lot of them are heavyweight&nbsp;&ndash; and some are expensive. Surprisingly, setting up monitoring for a Linux server running NGINX and PHP&#8209;FPM can still be a tedious task, especially for someone who\u2019s just starting with web development and NGINX.<\/p>\n<p>NGINX gained its popularity by being a lightweight and versatile solution for accelerating and securing modern web stacks. A similarly lightweight and versatile monitoring tool for NGINX seemed to be a good idea, and that\u2019s why we\u2019ve created Amplify.<\/p>\n<p>In fact, Amplify has started with the user community for the open source NGINX software as the focus. We\u2019re committed to making our open source products useful and powerful at all levels. Our experience with Amplify so far has demonstrated great success in adding to the power of NGINX.<\/p>\n<figure id=\"attachment_53078\" style=\"width: 964px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/cdn-1.wp.nginx.com\/wp-content\/uploads\/2017\/09\/Amplify-main-diagram-964x648@2x.png\" alt=\"NGINX Amplify screenshot\" width=\"964\" height=\"648\" class=\"size-full wp-image-53078\" \/><figcaption class=\"wp-caption-text\">Analyze and take control of your apps with NGINX Amplify<\/figcaption><\/figure>\n<p>Amplify is all about \u201cNGINX monitoring made easy\u201d and monitoring NGINX everywhere, whether your deployment is on-prem or in the cloud. Amplify is also an unprecedentedly low&#8209;barrier approach to NGINX monitoring. Start with three simple steps, and in under ten minutes you get all the key NGINX graphs, more than 100&nbsp;NGINX metrics, plus automated configuration file analysis and recommendations. And it\u2019s all based on many years of first&#8209;hand experience, coming directly from the NGINX core and support teams.<\/p>\n<p>Amplify is a tool made by NGINX for NGINX users that provides near&#8209;real&#8209;time monitoring. It collects hundreds of metrics from NGINX or NGINX&nbsp;Plus, log files, and the operating system, and provides a highly customizable interface to visualize them. The metrics can be aggregated over a cluster of NGINX instances for a high\u2011level overview, or fine&#8209;tuned to track the performance of individual services, APIs, or applications.<\/p>\n<p>Feature&#8209;wise, here\u2019s what Amplify is today:<\/p>\n<ul>\n<li><strong>Overview and SLA<\/strong>&nbsp;&ndash; A 30&#8209;second checkup of NGINX health. See aggregate visualizations for key metrics such as response time, the total sum of HTTP <code>5<em>xx<\/em><\/code> errors over the past 24&nbsp;hours, and more. Compare trends by switching time periods and instantly notice trends and abnormalities. SLA measurement is based on the Application Health Score index.<\/li>\n<li><strong>Graphs<\/strong>&nbsp;&ndash; A standard set of graphs for NGINX, PHP&#8209;FPM, and OS metrics. Graphs can be copied to user&#8209;defined dashboards for customization.<\/li>\n<li><strong>Analyzer<\/strong>&nbsp;&ndash; An overview of your NGINX configuration file, with alerts about common configuration problems. The static analyzer helps to improve performance, reliability, and security, based on recommendations from the NGINX team.<\/li>\n<li><strong>Dashboards<\/strong>&nbsp;&ndash; A dashboard where you can create your own graphs. Dashboards allow you to visualize more metrics, aggregate graphs across servers, set up custom metrics based on the NGINX log variables, and more. It\u2019s an easy&#8209;to&#8209;use and very flexible metric graphing instrument.<\/li>\n<li><strong>Alerts<\/strong>&nbsp;&ndash; Notifications about abnormal NGINX behavior. When an alert is triggered, Amplify sends a notification, and then monitors the situation until it reverts back to normal.<\/li>\n<li><strong>Inventory<\/strong>&nbsp;&ndash; The list of monitored systems. You can check hostnames, OS versions, and IP address information.<\/li>\n<\/ul>\n<p>During the beta phase, we had thousands of users sign up for Amplify. We\u2019ve been collecting close to a billion updates per day, and we\u2019re extremely grateful to everyone who has tried it out and provided feedback. A lot of what we\u2019ve added or changed in the past 12&nbsp;months has been based on user feedback.<\/p>\n<p>Here\u2019s some of what Amplify users have said:<\/p>\n<ul>\n<li>A very positive experience<\/li>\n<li>Very easy to install<\/li>\n<li>Instant visibility into NGINX performance\/behavior<\/li>\n<li>Outstanding NGINX monitoring capabilities, without many alternatives<\/li>\n<li>Useful, practical advice from the static analyzer&nbsp;&ndash; alleviates common configuration errors<\/li>\n<li>Gives insight into application quirks and errors from the NGINX vantage point<\/li>\n<li>Automated alerts are very helpful<\/li>\n<li>Nice, modern UI\/UX<\/li>\n<\/ul>\n<p>In the future, we\u2019ll be adding even more to Amplify. A few ideas we\u2019ve been working on recently include more plugins for monitoring, extensions to the static analyzer, improved alerting algorithms, availability testing, and more. If you have any ideas, feel free to share them with us!<\/p>\n<p>Amplify is available for all major Linux distributions, with experimental support for other OSs. For more detailed information on supported operating systems, please refer to the <a href=\"https:\/\/amplify.nginx.com\/docs\/faq-2-nginx-amplify-agent.html#21-what-operating-systems-are-supported\" target=\"_blank\">Amplify documentation<\/a>.<\/p>\n<p>Signing up for Amplify is easy&nbsp;&ndash; just visit <a target=\"_blank\" href=\"https:\/\/amplify.nginx.com\/\"><strong>amplify.nginx.com<\/strong><\/a>, provide a few basic details about yourself, and hit the <strong>Create<\/strong> button.<\/p>\n<p>For more information on Amplify, please refer to the official <a target=\"_blank\" href=\"https:\/\/amplify.nginx.com\/docs\/\">documentation<\/a> and <a>GitHub repo<\/a>.<\/p>\n<p>The post <a rel=\"nofollow\" href=\"https:\/\/www.nginx.com\/blog\/announcing-nginx-amplify-ga\/\">Announcing General Availability of NGINX Amplify<\/a> appeared first on <a rel=\"nofollow\" href=\"https:\/\/www.nginx.com\">NGINX<\/a>.<\/p>\n<p>Source: <a href=\"https:\/\/www.nginx.com\/blog\/announcing-nginx-amplify-ga\/\" target=\"_blank\">Announcing General Availability of NGINX Amplify<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<div class=\"mh-excerpt\"><p>Announcing General Availability of NGINX Amplify Have you been using NGINX, but still don\u2019t have real insights into its performance? Ever wonder whether a configuration snippet copied from somewhere is a valid one? Did you ever have issues with SSL configuration in NGINX? Do you want to make NGINX run even better? Or maybe you\u2019ve just been looking around for the simplest and quickest way to set up cloud monitoring for your LEMP stack? (Where the \u201cE\u201d in &#8220;LEMP&#8221; stems from \u201ceNGINe&#8209;X\u201d ?) A little over a year ago, we announced the public beta of NGINX Amplify&nbsp;&ndash; our own specialized, free monitoring tool for NGINX and NGINX&nbsp;Plus. Today, we\u2019re super excited to be removing the beta status for Amplify&nbsp;&ndash; it\u2019s now generally available (GA) for NGINX and NGINX&nbsp;Plus users. Amplify is production&#8209;ready, supported, and has a free&#8209;tier monitoring plan. Existing <a class=\"mh-excerpt-more\" href=\"https:\/\/jirak.net\/wp\/announcing-general-availability-of-nginx-amplify\/\" title=\"Announcing General Availability of NGINX Amplify\">[ more&#8230; ]<\/a><\/p>\n<\/div>","protected":false},"author":1,"featured_media":18748,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[169],"tags":[652],"class_list":["post-18747","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-nginx"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/18747","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/comments?post=18747"}],"version-history":[{"count":1,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/18747\/revisions"}],"predecessor-version":[{"id":18749,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/18747\/revisions\/18749"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/media\/18748"}],"wp:attachment":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/media?parent=18747"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/categories?post=18747"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/tags?post=18747"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}