1VARNISH-COUNTERS(7) VARNISH-COUNTERS(7)
2
6 varnish-counters - Varnish counter field definitions
7
9 summs – counter - debug
10 stat summ operations
11 Number of times per-thread statistics were summed into the global
13 counters.
14 uptime – counter - info
16 Child process uptime
17 How long the child process has been running.
19 sess_conn – counter - info
21 Sessions accepted
22 Count of sessions successfully accepted
24 sess_fail – counter - info
26 Session accept failures
27 Count of failures to accept TCP connection.
29 This counter is the sum of the sess_fail_* counters, which give more
31 detailed information.
32 sess_fail_econnaborted – counter - info
34 Session accept failures: connection aborted
35 Detailed reason for sess_fail: Connection aborted by the client,
37 usually harmless.
38 sess_fail_eintr – counter - info
40 Session accept failures: interrupted system call
41 Detailed reason for sess_fail: The accept() call was interrupted,
43 usually harmless
44 sess_fail_emfile – counter - info
46 Session accept failures: too many open files
47 Detailed reason for sess_fail: No file descriptor was available.
49 Consider raising RLIMIT_NOFILE (see ulimit -n).
50 sess_fail_ebadf – counter - info
52 Session accept failures: bad file descriptor
53 Detailed reason for sess_fail: The listen socket file descriptor was
55 invalid. Should never happen.
56 sess_fail_enomem – counter - info
58 Session accept failures: not enough memory
59 Detailed reason for sess_fail: Most likely insufficient socket buf‐
61 fer memory. Should never happen
62 sess_fail_other – counter - info
64 Session accept failures: other
65 Detailed reason for sess_fail: neither of the above, see SessError
67 log (varnishlog -g raw -i SessError).
68 client_req_400 – counter - info
70 Client requests received, subject to 400 errors
71 400 means we couldn't make sense of the request, it was malformed in
73 some drastic way.
74 client_req_417 – counter - info
76 Client requests received, subject to 417 errors
77 417 means that something went wrong with an Expect: header.
79 client_req – counter - info
81 Good client requests received
82 The count of parseable client requests seen.
84 esi_req – counter - info
86 ESI subrequests
87 Number of ESI subrequests made.
89 cache_hit – counter - info
91 Cache hits
92 Count of cache hits. A cache hit indicates that an object has been
94 delivered to a client without fetching it from a backend server.
95 cache_hit_grace – counter - info
97 Cache grace hits
98 Count of cache hits with grace. A cache hit with grace is a cache
100 hit where the object is expired. Note that such hits are also in‐
101 cluded in the cache_hit counter.
102 cache_hitpass – counter - info
104 Cache hits for pass.
105 Count of hits for pass. A cache hit for pass indicates that Varnish
107 is going to pass the request to the backend and this decision has
108 been cached in it self. This counts how many times the cached deci‐
109 sion is being used.
110 cache_hitmiss – counter - info
112 Cache hits for miss.
113 Count of hits for miss. A cache hit for miss indicates that Varnish
115 is going to proceed as for a cache miss without request coalescing,
116 and this decision has been cached. This counts how many times the
117 cached decision is being used.
118 cache_miss – counter - info
120 Cache misses
121 Count of misses. A cache miss indicates the object was fetched from
123 the backend before delivering it to the client.
124 beresp_uncacheable – counter - info
126 Uncacheable backend responses
127 Count of backend responses considered uncacheable.
129 beresp_shortlived – counter - info
131 Shortlived objects
132 Count of objects created with ttl+grace+keep shorter than the
134 'shortlived' runtime parameter.
135 backend_conn – counter - info
137 Backend conn. success
138 How many backend connections have successfully been established.
140 backend_unhealthy – counter - info
142 Backend conn. not attempted
143 backend_busy – counter - info
145 Backend conn. too many
146 backend_fail – counter - info
148 Backend conn. failures
149 backend_reuse – counter - info
151 Backend conn. reuses
152 Count of backend connection reuses. This counter is increased when‐
154 ever we reuse a recycled connection.
155 backend_recycle – counter - info
157 Backend conn. recycles
158 Count of backend connection recycles. This counter is increased
160 whenever we have a keep-alive connection that is put back into the
161 pool of connections. It has not yet been used, but it might be, un‐
162 less the backend closes it.
163 backend_retry – counter - info
165 Backend conn. retry
166 fetch_head – counter - info
168 Fetch no body (HEAD)
169 beresp with no body because the request is HEAD.
171 fetch_length – counter - info
173 Fetch with Length
174 beresp.body with Content-Length.
176 fetch_chunked – counter - info
178 Fetch chunked
179 beresp.body with Chunked.
181 fetch_eof – counter - info
183 Fetch EOF
184 beresp.body with EOF.
186 fetch_bad – counter - info
188 Fetch bad T-E
189 beresp.body length/fetch could not be determined.
191 fetch_none – counter - info
193 Fetch no body
194 beresp.body empty
196 fetch_1xx – counter - info
198 Fetch no body (1xx)
199 beresp with no body because of 1XX response.
201 fetch_204 – counter - info
203 Fetch no body (204)
204 beresp with no body because of 204 response.
206 fetch_304 – counter - info
208 Fetch no body (304)
209 beresp with no body because of 304 response.
211 fetch_failed – counter - info
213 Fetch failed (all causes)
214 beresp fetch failed.
216 bgfetch_no_thread – counter - info
218 Background fetch failed (no thread)
219 A bgfetch triggered by a grace hit failed, no thread available.
221 pools – gauge - info
223 Number of thread pools
224 Number of thread pools. See also parameter thread_pools. NB: Pres‐
226 ently pools cannot be removed once created.
227 threads – gauge - info
229 Total number of threads
230 Number of threads in all pools. See also parameters thread_pools,
232 thread_pool_min and thread_pool_max.
233 threads_limited – counter - info
235 Threads hit max
236 Number of times more threads were needed, but limit was reached in a
238 thread pool. See also parameter thread_pool_max.
239 threads_created – counter - info
241 Threads created
242 Total number of threads created in all pools.
244 threads_destroyed – counter - info
246 Threads destroyed
247 Total number of threads destroyed in all pools.
249 threads_failed – counter - info
251 Thread creation failed
252 Number of times creating a thread failed. See VSL::Debug for diag‐
254 nostics. See also parameter thread_fail_delay.
255 thread_queue_len – gauge - info
257 Length of session queue
258 Length of session queue waiting for threads. NB: Only updates once
260 per second. See also parameter thread_queue_limit.
261 busy_sleep – counter - info
263 Number of requests sent to sleep on busy objhdr
264 Number of requests sent to sleep without a worker thread because
266 they found a busy object.
267 busy_wakeup – counter - info
269 Number of requests woken after sleep on busy objhdr
270 Number of requests taken off the busy object sleep list and resched‐
272 uled.
273 busy_killed – counter - info
275 Number of requests killed after sleep on busy objhdr
276 Number of requests killed from the busy object sleep list due to
278 lack of resources.
279 sess_queued – counter - info
281 Sessions queued for thread
282 Number of times session was queued waiting for a thread. See also
284 parameter thread_queue_limit.
285 sess_dropped – counter - info
287 Sessions dropped for thread
288 Number of times an HTTP/1 session was dropped because the queue was
290 too long already. See also parameter thread_queue_limit.
291 req_dropped – counter - info
293 Requests dropped
294 Number of times an HTTP/2 stream was refused because the queue was
296 too long already. See also parameter thread_queue_limit.
297 n_object – gauge - info
299 object structs made
300 Approximate number of HTTP objects (headers + body, if present) in
302 the cache.
303 n_vampireobject – gauge - diag
305 unresurrected objects
306 Number of unresurrected objects
308 n_objectcore – gauge - info
310 objectcore structs made
311 Approximate number of object metadata elements in the cache. Each
313 object needs an objectcore, extra objectcores are for hit-for-miss,
314 hit-for-pass and busy objects.
315 n_objecthead – gauge - info
317 objecthead structs made
318 Approximate number of different hash entries in the cache.
320 n_backend – gauge - info
322 Number of backends
323 Number of backends known to us.
325 n_expired – counter - info
327 Number of expired objects
328 Number of objects that expired from cache because of old age.
330 n_lru_nuked – counter - info
332 Number of LRU nuked objects
333 How many objects have been forcefully evicted from storage to make
335 room for a new object.
336 n_lru_moved – counter - diag
338 Number of LRU moved objects
339 Number of move operations done on the LRU list.
341 n_lru_limited – counter - info
343 Reached nuke_limit
344 Number of times more storage space were needed, but limit was
346 reached in a nuke_limit. See also parameter nuke_limit.
347 losthdr – counter - info
349 HTTP header overflows
350 s_sess – counter - info
352 Total sessions seen
353 n_pipe – gauge - info
355 Number of ongoing pipe sessions
356 pipe_limited – counter - info
358 Pipes hit pipe_sess_max
359 Number of times more pipes were needed, but the limit was reached.
361 See also parameter pipe_sess_max.
362 s_pipe – counter - info
364 Total pipe sessions seen
365 s_pass – counter - info
367 Total pass-ed requests seen
368 s_fetch – counter - info
370 Total backend fetches initiated
371 Total backend fetches initiated, including background fetches.
373 s_bgfetch – counter - info
375 Total backend background fetches initiated
376 s_synth – counter - info
378 Total synthetic responses made
379 s_req_hdrbytes – counter - info
381 Request header bytes
382 Total request header bytes received
384 s_req_bodybytes – counter - info
386 Request body bytes
387 Total request body bytes received
389 s_resp_hdrbytes – counter - info
391 Response header bytes
392 Total response header bytes transmitted
394 s_resp_bodybytes – counter - info
396 Response body bytes
397 Total response body bytes transmitted
399 s_pipe_hdrbytes – counter - info
401 Pipe request header bytes
402 Total request bytes received for piped sessions
404 s_pipe_in – counter - info
406 Piped bytes from client
407 Total number of bytes forwarded from clients in pipe sessions
409 s_pipe_out – counter - info
411 Piped bytes to client
412 Total number of bytes forwarded to clients in pipe sessions
414 sess_closed – counter - info
416 Session Closed
417 sess_closed_err – counter - info
419 Session Closed with error
420 Total number of sessions closed with errors. See sc_* diag counters
422 for detailed breakdown
423 sess_readahead – counter - info
425 Session Read Ahead
426 sess_herd – counter - diag
428 Session herd
429 Number of times the timeout_linger triggered
431 sc_rem_close – counter - diag
433 Session OK REM_CLOSE
434 Number of session closes with REM_CLOSE (Client Closed)
436 sc_req_close – counter - diag
438 Session OK REQ_CLOSE
439 Number of session closes with REQ_CLOSE (Client requested close)
441 sc_req_http10 – counter - diag
443 Session Err REQ_HTTP10
444 Number of session closes with Error REQ_HTTP10 (Proto < HTTP/1.1)
446 sc_rx_bad – counter - diag
448 Session Err RX_BAD
449 Number of session closes with Error RX_BAD (Received bad req/resp)
451 sc_rx_body – counter - diag
453 Session Err RX_BODY
454 Number of session closes with Error RX_BODY (Failure receiving
456 req.body)
457 sc_rx_junk – counter - diag
459 Session Err RX_JUNK
460 Number of session closes with Error RX_JUNK (Received junk data)
462 sc_rx_overflow – counter - diag
464 Session Err RX_OVERFLOW
465 Number of session closes with Error RX_OVERFLOW (Received buffer
467 overflow)
468 sc_rx_timeout – counter - diag
470 Session Err RX_TIMEOUT
471 Number of session closes with Error RX_TIMEOUT (Receive timeout)
473 sc_rx_close_idle – counter - diag
475 Session Err RX_CLOSE_IDLE
476 Number of session closes with Error RX_CLOSE_IDLE: timeout_idle has
478 been exceeded while waiting for a client request.
479 sc_tx_pipe – counter - diag
481 Session OK TX_PIPE
482 Number of session closes with TX_PIPE (Piped transaction)
484 sc_tx_error – counter - diag
486 Session Err TX_ERROR
487 Number of session closes with Error TX_ERROR (Error transaction)
489 sc_tx_eof – counter - diag
491 Session OK TX_EOF
492 Number of session closes with TX_EOF (EOF transmission)
494 sc_resp_close – counter - diag
496 Session OK RESP_CLOSE
497 Number of session closes with RESP_CLOSE (Backend/VCL requested
499 close)
500 sc_overload – counter - diag
502 Session Err OVERLOAD
503 Number of session closes with Error OVERLOAD (Out of some resource)
505 sc_pipe_overflow – counter - diag
507 Session Err PIPE_OVERFLOW
508 Number of session closes with Error PIPE_OVERFLOW (Session pipe
510 overflow)
511 sc_range_short – counter - diag
513 Session Err RANGE_SHORT
514 Number of session closes with Error RANGE_SHORT (Insufficient data
516 for range)
517 sc_req_http20 – counter - diag
519 Session Err REQ_HTTP20
520 Number of session closes with Error REQ_HTTP20 (HTTP2 not accepted)
522 sc_vcl_failure – counter - diag
524 Session Err VCL_FAILURE
525 Number of session closes with Error VCL_FAILURE (VCL failure)
527 client_resp_500 – counter - diag
529 Delivery failed due to insufficient workspace.
530 Number of times we failed a response due to running out of workspace
532 memory during delivery.
533 ws_backend_overflow – counter - diag
535 workspace_backend overflows
536 Number of times we ran out of space in workspace_backend.
538 ws_client_overflow – counter - diag
540 workspace_client overflows
541 Number of times we ran out of space in workspace_client.
543 ws_thread_overflow – counter - diag
545 workspace_thread overflows
546 Number of times we ran out of space in workspace_thread.
548 ws_session_overflow – counter - diag
550 workspace_session overflows
551 Number of times we ran out of space in workspace_session.
553 shm_records – counter - diag
555 SHM records
556 Number of log records written to the shared memory log.
558 shm_writes – counter - diag
560 SHM writes
561 Number of individual writes to the shared memory log. A single write
563 may batch multiple records for bufferred tasks.
564 shm_flushes – counter - diag
566 SHM flushes due to overflow
567 Number of writes performed before the end of a bufferred task be‐
569 cause adding a record to a batch would exceed vsl_buffer.
570 shm_cont – counter - diag
572 SHM lock contention
573 Number of times a write had to wait for the lock.
575 shm_cycles – counter - diag
577 SHM cycles through VSL space
578 Number of times a write of log records would reach past the end of
580 the shared memory log, cycling back to the beginning.
581 shm_bytes – counter - diag
583 SHM bytes
584 Number of bytes written to the shared memory log.
586 backend_req – counter - info
588 Backend requests made
589 n_vcl – gauge - info
591 Number of loaded VCLs in total
592 n_vcl_avail – gauge - diag
594 Number of VCLs available
595 n_vcl_discard – gauge - diag
597 Number of discarded VCLs
598 vcl_fail – counter - info
600 VCL failures
601 Count of failures which prevented VCL from completing.
603 bans – gauge - info
605 Count of bans
606 Number of all bans in system, including bans superseded by newer
608 bans and bans already checked by the ban-lurker.
609 bans_completed – gauge - diag
611 Number of bans marked 'completed'
612 Number of bans which are no longer active, either because they got
614 checked by the ban-lurker or superseded by newer identical bans.
615 bans_obj – gauge - diag
617 Number of bans using obj.*
618 Number of bans which use obj.* variables. These bans can possibly
620 be washed by the ban-lurker.
621 bans_req – gauge - diag
623 Number of bans using req.*
624 Number of bans which use req.* variables. These bans can not be
626 washed by the ban-lurker.
627 bans_added – counter - diag
629 Bans added
630 Counter of bans added to ban list.
632 bans_deleted – counter - diag
634 Bans deleted
635 Counter of bans deleted from ban list.
637 bans_tested – counter - diag
639 Bans tested against objects (lookup)
640 Count of how many bans and objects have been tested against each
642 other during hash lookup.
643 bans_obj_killed – counter - diag
645 Objects killed by bans (lookup)
646 Number of objects killed by bans during object lookup.
648 bans_lurker_tested – counter - diag
650 Bans tested against objects (lurker)
651 Count of how many bans and objects have been tested against each
653 other by the ban-lurker.
654 bans_tests_tested – counter - diag
656 Ban tests tested against objects (lookup)
657 Count of how many tests and objects have been tested against each
659 other during lookup. 'ban req.url == foo && req.http.host == bar'
660 counts as one in 'bans_tested' and as two in 'bans_tests_tested'
661 bans_lurker_tests_tested – counter - diag
663 Ban tests tested against objects (lurker)
664 Count of how many tests and objects have been tested against each
666 other by the ban-lurker. 'ban req.url == foo && req.http.host ==
667 bar' counts as one in 'bans_tested' and as two in
668 'bans_tests_tested'
669 bans_lurker_obj_killed – counter - diag
671 Objects killed by bans (lurker)
672 Number of objects killed by the ban-lurker.
674 bans_lurker_obj_killed_cutoff – counter - diag
676 Objects killed by bans for cutoff (lurker)
677 Number of objects killed by the ban-lurker to keep the number of
679 bans below ban_cutoff.
680 bans_dups – counter - diag
682 Bans superseded by other bans
683 Count of bans replaced by later identical bans.
685 bans_lurker_contention – counter - diag
687 Lurker gave way for lookup
688 Number of times the ban-lurker had to wait for lookups.
690 bans_persisted_bytes – gauge - diag
692 Bytes used by the persisted ban lists
693 Number of bytes used by the persisted ban lists.
695 bans_persisted_fragmentation – gauge - diag
697 Extra bytes in persisted ban lists due to fragmentation
698 Number of extra bytes accumulated through dropped and completed bans
700 in the persistent ban lists.
701 n_purges – counter - info
703 Number of purge operations executed
704 n_obj_purged – counter - info
706 Number of purged objects
707 exp_mailed – counter - diag
709 Number of objects mailed to expiry thread
710 Number of objects mailed to expiry thread for handling.
712 exp_received – counter - diag
714 Number of objects received by expiry thread
715 Number of objects received by expiry thread for handling.
717 hcb_nolock – counter - debug
719 HCB Lookups without lock
720 hcb_lock – counter - debug
722 HCB Lookups with lock
723 hcb_insert – counter - debug
725 HCB Inserts
726 esi_errors – counter - diag
728 ESI parse errors (unlock)
729 esi_warnings – counter - diag
731 ESI parse warnings (unlock)
732 vmods – gauge - info
734 Loaded VMODs
735 n_gzip – counter - info
737 Gzip operations
738 n_gunzip – counter - info
740 Gunzip operations
741 n_test_gunzip – counter - info
743 Test gunzip operations
744 Those operations occur when Varnish receives a compressed object
746 from a backend. They are done to verify the gzip stream while it's
747 inserted in storage.
748
750 uptime – counter - info
751 Management process uptime
752 Uptime in seconds of the management process
754 child_start – counter - diag
756 Child process started
757 Number of times the child process has been started
759 child_exit – counter - diag
761 Child process normal exit
762 Number of times the child process has been cleanly stopped
764 child_stop – counter - diag
766 Child process unexpected exit
767 Number of times the child process has exited with an unexpected re‐
769 turn code
770 child_died – counter - diag
772 Child process died (signal)
773 Number of times the child process has died due to signals
775 child_dump – counter - diag
777 Child process core dumped
778 Number of times the child process has produced core dumps
780 child_panic – counter - diag
782 Child process panic
783 Number of times the management process has caught a child panic
785
787 live – gauge - debug
788 In use
789 pool – gauge - debug
791 In Pool
792 sz_wanted – gauge - debug
794 Size requested
795 sz_actual – gauge - debug
797 Size allocated
798 allocs – counter - debug
800 Allocations
801 frees – counter - debug
803 Frees
804 recycle – counter - debug
806 Recycled from pool
807 timeout – counter - debug
809 Timed out from pool
810 toosmall – counter - debug
812 Too small to recycle
813 surplus – counter - debug
815 Too many for pool
816 randry – counter - debug
818 Pool ran dry
819
821 c_req – counter - info
822 Allocator requests
823 Number of times the storage has been asked to provide a storage seg‐
825 ment.
826 c_fail – counter - info
828 Allocator failures
829 Number of times the storage has failed to provide a storage segment.
831 c_bytes – counter - info
833 Bytes allocated
834 Number of total bytes allocated by this storage.
836 c_freed – counter - info
838 Bytes freed
839 Number of total bytes returned to this storage.
841 g_alloc – gauge - info
843 Allocations outstanding
844 Number of storage allocations outstanding.
846 g_bytes – gauge - info
848 Bytes outstanding
849 Number of bytes allocated from the storage.
851 g_space – gauge - info
853 Bytes available
854 Number of bytes left in the storage.
856
858 c_req – counter - info
859 Allocator requests
860 Number of times the storage has been asked to provide a storage seg‐
862 ment.
863 c_fail – counter - info
865 Allocator failures
866 Number of times the storage has failed to provide a storage segment.
868 c_bytes – counter - info
870 Bytes allocated
871 Number of total bytes allocated by this storage.
873 c_freed – counter - info
875 Bytes freed
876 Number of total bytes returned to this storage.
878 g_alloc – gauge - info
880 Allocations outstanding
881 Number of storage allocations outstanding.
883 g_bytes – gauge - info
885 Bytes outstanding
886 Number of bytes allocated from the storage.
888 g_space – gauge - info
890 Bytes available
891 Number of bytes left in the storage.
893
895 c_req – counter - info
896 Allocator requests
897 Number of times the storage has been asked to provide a storage seg‐
899 ment.
900 c_fail – counter - info
902 Allocator failures
903 Number of times the storage has failed to provide a storage segment.
905 c_bytes – counter - info
907 Bytes allocated
908 Number of total bytes allocated by this storage.
910 c_freed – counter - info
912 Bytes freed
913 Number of total bytes returned to this storage.
915 g_alloc – gauge - info
917 Allocations outstanding
918 Number of storage allocations outstanding.
920 g_bytes – gauge - info
922 Bytes outstanding
923 Number of bytes allocated from the storage.
925 g_space – gauge - info
927 Bytes available
928 Number of bytes left in the storage.
930 g_smf – gauge - info
932 N struct smf
933 g_smf_frag – gauge - info
935 N small free smf
936 g_smf_large – gauge - info
938 N large free smf
939
941 happy – bitmap - info
942 Happy health probes
943 Represents the last probe results as a bitmap. Happy probes are bits
945 set to 1, and the unhappy ones are set to 0. The highest bits repre‐
946 sent the oldest probes.
947 bereq_hdrbytes – counter - info
949 Request header bytes
950 Total backend request header bytes sent
952 bereq_bodybytes – counter - info
954 Request body bytes
955 Total backend request body bytes sent
957 beresp_hdrbytes – counter - info
959 Response header bytes
960 Total backend response header bytes received
962 beresp_bodybytes – counter - info
964 Response body bytes
965 Total backend response body bytes received
967 pipe_hdrbytes – counter - info
969 Pipe request header bytes
970 Total request bytes sent for piped sessions
972 pipe_out – counter - info
974 Piped bytes to backend
975 Total number of bytes forwarded to backend in pipe sessions
977 pipe_in – counter - info
979 Piped bytes from backend
980 Total number of bytes forwarded from backend in pipe sessions
982 conn – gauge - info
984 Concurrent connections used
985 The number of currently used connections to the backend. This number
987 is always less or equal to the number of connections to the backend
988 (as, for example shown as ESTABLISHED for TCP connections in net‐
989 stat) due to connection pooling.
990 req – counter - info
992 Backend requests sent
993 unhealthy – counter - info
995 Fetches not attempted due to backend being unhealthy
996 busy – counter - info
998 Fetches not attempted due to backend being busy
999 Number of times the max_connections limit was reached
1001 fail – counter - info
1003 Connections failed
1004 Counter of failed opens. Detailed reasons are given in the fail_*
1006 counters (DIAG level) and in the log under the FetchError tag.
1007 This counter is the sum of all detailed fail_* counters.
1009 All fail_* counters may be slightly inaccurate for efficiency.
1011 fail_eacces – counter - diag
1013 Connections failed with EACCES or EPERM
1014 fail_eaddrnotavail – counter - diag
1016 Connections failed with EADDRNOTAVAIL
1017 fail_econnrefused – counter - diag
1019 Connections failed with ECONNREFUSED
1020 fail_enetunreach – counter - diag
1022 Connections failed with ENETUNREACH
1023 fail_etimedout – counter - diag
1025 Connections failed ETIMEDOUT
1026 fail_other – counter - diag
1028 Connections failed for other reason
1029 helddown – counter - diag
1031 Connection opens not attempted
1032 Connections not attempted during the backend_local_error_holddown or
1034 backend_remote_error_holddown interval after a fundamental connec‐
1035 tion issue.
1036
1038 Counters which track the activity in the different classes of mu‐
1039 tex-locks.
1040 The counts may be slightly wrong if there are more than one lock in‐
1042 stantiated in each class (ie: .creat > 1)
1043 creat – counter - debug
1045 Created locks
1046 destroy – counter - debug
1048 Destroyed locks
1049 locks – counter - debug
1051 Lock Operations
1052 dbg_busy – counter - debug
1054 Contended lock operations
1055 If the lck debug bit is set: Lock operations which returned EBUSY on
1057 the first locking attempt.
1058 If the lck debug bit is unset, this counter will never be incre‐
1060 mented even if lock operations are contended.
1061 dbg_try_fail – counter - debug
1063 Contended trylock operations
1064 If the lck debug bit is set: Trylock operations which returned
1066 EBUSY.
1067 If the lck debug bit is unset, this counter will never be incre‐
1069 mented even if lock operations are contended.
1070
1072 This man page was written by Lasse Karstensen, using content from
1073 vsc2rst written by Tollef Fog Heen.
1074 VARNISH-COUNTERS(7)