[5.2] 7ca8c0c What's new? VUT

PÃ¥l Hermunn Johansen hermunn at varnish-software.com
Fri Sep 15 11:17:27 UTC 2017

commit 7ca8c0c4a5888200128ddcb1cfaff915f71b6070
Author: Dridi Boukelmoune <dridi.boukelmoune at gmail.com>
Date:   Wed Sep 13 16:48:39 2017 +0200

    What's new? VUT

diff --git a/doc/sphinx/whats-new/changes-5.2.rst b/doc/sphinx/whats-new/changes-5.2.rst
index 7dced4d..b9585ce 100644
--- a/doc/sphinx/whats-new/changes-5.2.rst
+++ b/doc/sphinx/whats-new/changes-5.2.rst
@@ -156,9 +156,26 @@ does not require strict ABI compliance.
 .. _whatsnew_vut_5.2:
-XXX: document once merged
+Added VUT API
+One way to extend Varnish is to write VSM clients, programs that tap
+into the Varnish Shared Memory (VSM) usually via ``libvarnishapi`` or
+community bindings for other languages than C. Varnish already ships
+with VUTs (Varnish UTilities) that either process the Varnish Shared
+Log (VSL) like ``varnishlog`` or ``varnishncsa`` or the Varnish Shared
+Counters (VSC) like ``varnishstat``.
+Most of the setup for these programs is similar, and so they shared an
+API that is now available outside of the Varnish source tree. The VUT
+API has been cleaned up to remove assumptions made for our utilities.
+It hides most of the complexity and redundancy of setting up a log
+processor and helps you focus on your functionality. If you use
+autotools for building, a new macro in ``varnish.m4`` removes some of
+the boilerplate to generate part of the documentation.
+We hope that much like VMODs we will see new tools that take advantage
+of this API to extend Varnish in new ways much like VMODs made it easy
+to add new functionality to VCL.

More information about the varnish-commit mailing list