summaryrefslogtreecommitdiffstats
path: root/_build/content/articles/ranch-2.1.0.asciidoc
diff options
context:
space:
mode:
Diffstat (limited to '_build/content/articles/ranch-2.1.0.asciidoc')
-rw-r--r--_build/content/articles/ranch-2.1.0.asciidoc45
1 files changed, 45 insertions, 0 deletions
diff --git a/_build/content/articles/ranch-2.1.0.asciidoc b/_build/content/articles/ranch-2.1.0.asciidoc
new file mode 100644
index 00000000..c653a516
--- /dev/null
+++ b/_build/content/articles/ranch-2.1.0.asciidoc
@@ -0,0 +1,45 @@
++++
+date = "2021-09-09T07:00:00+01:00"
+title = "Ranch 2.1"
+
++++
+
+Ranch `2.1.0` has been released!
+
+Ranch 2.1 adds counters for the number of connections
+accepted and terminated. They can be used to produce
+information about accept or shutdown rates or as a
+total number of connections handled by Ranch.
+
+Ranch 2.1 also adds an alarm around the number of
+active connections a connection supervisor handles.
+When that number is high it is now possible to
+automatically perform an action, such as logging
+or gracefully shutting down idle connections.
+
+Starting from Ranch 2.1 the `{inet_backend,socket}`
+option is accepted for TCP listeners. Ranch tests
+now also run with this option enabled. Note that
+there are known issues with the socket backend
+at this time.
+
+We are providing a
+https://github.com/juhlig/prometheus_ranch[Prometheus collector]
+as a separate project as well as a
+https://github.com/juhlig/prometheus_ranch/blob/master/dashboards/ranch-dashboard.json[Grafana dashboard].
+
+Thanks this time go to Jan Uhlig and Maria Scott
+for contributing the alarms and counters as well
+as other improvements that went into this release.
+
+Ranch 2.1 requires Erlang/OTP 22 or above and is tested and supported
+on Linux, FreeBSD, macOS and Windows.
+
+A complete list of changes can be found in the migration guide:
+https://ninenines.eu/docs/en/ranch/2.1/guide/migrating_from_2.0/[Migrating from Ranch 2.0 to 2.1].
+
+You can donate to this project via
+https://github.com/sponsors/essen[GitHub Sponsors].
+
+As usual, feedback is appreciated, and issues or
+questions should be sent via Github tickets. Thanks!