Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
a45319c5
Commit
a45319c5
authored
Sep 09, 2020
by
Dridi Boukelmoune
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: Release notes for varnishstat
parent
a7055b35
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
48 additions
and
1 deletion
+48
-1
changes-trunk.rst
doc/sphinx/whats-new/changes-trunk.rst
+17
-1
upgrading-trunk.rst
doc/sphinx/whats-new/upgrading-trunk.rst
+31
-0
No files found.
doc/sphinx/whats-new/changes-trunk.rst
View file @
a45319c5
...
...
@@ -57,7 +57,23 @@ varnishadm
varnishstat
===========
**XXX changes concerning varnishstat(1) and/or varnish-counters(7)**
A help screen is now available in interactive mode via the ``h`` key.
Again in interactive mode, verbosity is increased from the default value
during startup when the filtering of counters would otherwise display
nothing.
Filtering using the ``-f`` option is now deprecated in favor of ``-I`` and
``-X`` options that are treated in order. While still present, the ``-f``
option now also work in order instead of exclusive filters first and then
inclusive filters. It was also wrongly documented as inclusive first.
The JSON output slightly changed to more easily be consumed with programming
languages that may map JSON objects to types. See upgrade notes for more
details.
There are two new ``MAIN.beresp_uncacheable`` and ``MAIN.beresp_shortlived``
counters.
varnishtest
===========
...
...
doc/sphinx/whats-new/upgrading-trunk.rst
View file @
a45319c5
...
...
@@ -30,4 +30,35 @@ to:**
* Changes in public APIs that may require changes in VMODs or VAPI/VUT
clients.
varnishstat
===========
The JSON output (``-j`` option) changed to avoid having the ``timestamp``
field mixed with the counters fields. As such the schema version was bumped
from 0 to 1, and a ``version`` top-level field was added to keep track of
future schema changes. Counters are in a new ``counters`` top-level field.
Before::
{
"timestamp": "YYYY-mm-ddTHH:MM:SS",
"MGT.uptime": {
...
},
...
}
After::
{
"version": 1,
"timestamp": "YYYY-mm-ddTHH:MM:SS",
"counters": {
"MGT.uptime": {
...
},
...
}
}
*eof*
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment