Skip to technology filters Skip to main content
Dynatrace Hub

Extend the platform,
empower your team.

Popular searches:
Home hero bg
Varnish CacheVarnish Cache
Varnish Cache

Varnish Cache

Monitor the statistics of your Varnish Cache instances.

Extension
Free trialDocumentation
Platform overview dashboardClassic overview dashboardInstance view
  • Product information
  • Release notes

Overview

Monitor the statistics of Varnish Cache instances

Use cases

  • Monitor the health and state of Varnish cache instances
  • Detect and alert on anomalous behavior
  • Understand the load and operational performance of the cache

Get started

For more information on the installation and configuration, please see Varnish Cache extension in the Dynatrace Documentation.

Details

Compatibility information

Varnish v. 6.2.1+

Dynatrace
Documentation
By Dynatrace
Dynatrace support center
Subscribe to new releases
Copy to clipboard

Feature sets

Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.

Feature setsNumber of metrics included
Metric nameMetric keyDescriptionUnit
In usevarnish.cache.mempool.liveIn useCount
In Poolvarnish.cache.mempool.poolIn PoolCount
Size requestedvarnish.cache.mempool.sz_wantedSize requestedByte
Size allocatedvarnish.cache.mempool.sz_actualSize allocatedByte
Allocationsvarnish.cache.mempool.allocs.countAllocationsCount
Freesvarnish.cache.mempool.frees.countFreesCount
Recycled from poolvarnish.cache.mempool.recycle.countRecycled from poolCount
Timed out from poolvarnish.cache.mempool.timeout.countTimed out from poolCount
Too small to recyclevarnish.cache.mempool.toosmall.countToo small to recycleCount
Too many for poolvarnish.cache.mempool.surplus.countToo many for poolCount
Pool ran dryvarnish.cache.mempool.randry.countPool ran dryCount
Metric nameMetric keyDescriptionUnit
Created locksvarnish.cache.lck.creat.countCreated locksCount
Destroyed locksvarnish.cache.lck.destroy.countDestroyed locksCount
Lock Operationsvarnish.cache.lck.locks.countLock OperationsCount
Contended lock operationsvarnish.cache.lck.dbg_busy.countIf the lck debug bit is set: Lock operations which returned EBUSY on the first locking attempt. If the lck debug bit is unset, this counter will never be incremented even if lock operations are contended.Count
Contended trylock operationsvarnish.cache.lck.dbg_try_fail.countIf the lck debug bit is set: Trylock operations which returned EBUSY. If the lck debug bit is unset, this counter will never be incremented even if lock operations are contended.Count
Metric nameMetric keyDescriptionUnit
Happy health probesvarnish.cache.vbe.happyRepresents the last probe results as a bitmap. Happy probes are bits set to 1, and the unhappy ones are set to 0. The highest bits represent the oldest probes.Unspecified
Request header bytesvarnish.cache.vbe.bereq_hdrbytes.countTotal backend request header bytes sentByte
Request body bytesvarnish.cache.vbe.bereq_bodybytes.countTotal backend request body bytes sentByte
Response header bytesvarnish.cache.vbe.beresp_hdrbytes.countTotal backend response header bytes receivedByte
Response body bytesvarnish.cache.vbe.beresp_bodybytes.countTotal backend response body bytes receivedByte
Pipe request header bytesvarnish.cache.vbe.pipe_hdrbytes.countTotal request bytes sent for piped sessionsByte
Piped bytes to backendvarnish.cache.vbe.pipe_out.countTotal number of bytes forwarded to backend in pipe sessionsByte
Piped bytes from backendvarnish.cache.vbe.pipe_in.countTotal number of bytes forwarded from backend in pipe sessionsByte
Concurrent connections usedvarnish.cache.vbe.connThe number of currently used connections to the backend. This number is always less or equal to the number of connections to the backend (as, for example shown as ESTABLISHED for TCP connections in netstat) due to connection pooling.Count
Backend requests sentvarnish.cache.vbe.req.countBackend requests sentCount
Fetches not attempted due to backend being unhealthyvarnish.cache.vbe.unhealthy.countFetches not attempted due to backend being unhealthyCount
Fetches not attempted due to backend being busyvarnish.cache.vbe.busy.countNumber of times the max_connections limit was reached .. === Anything below is actually per VCP entry, but collected per === backend for simplicityCount
Connections failedvarnish.cache.vbe.fail.countCounter of failed opens. Detailed reasons are given in the fail_* counters (DIAG level) and in the log under the FetchError tag. This counter is the sum of all detailed fail_* counters. All fail_* counters may be slightly inaccurate for efficiency.Count
Connections failed with EACCES or EPERMvarnish.cache.vbe.fail_eacces.countConnections failed with EACCES or EPERMCount
Connections failed with EADDRNOTAVAILvarnish.cache.vbe.fail_eaddrnotavail.countConnections failed with EADDRNOTAVAILCount
Connections failed with ECONNREFUSEDvarnish.cache.vbe.fail_econnrefused.countConnections failed with ECONNREFUSEDCount
Connections failed with ENETUNREACHvarnish.cache.vbe.fail_enetunreach.countConnections failed with ENETUNREACHCount
Connections failed ETIMEDOUTvarnish.cache.vbe.fail_etimedout.countConnections failed ETIMEDOUTCount
Connections failed for other reasonvarnish.cache.vbe.fail_other.countConnections failed for other reasonCount
Connection opens not attemptedvarnish.cache.vbe.helddown.countConnections not attempted during the backend_local_error_holddown or backend_remote_error_holddown interval after a fundamental connection issue.Count
Metric nameMetric keyDescriptionUnit
Management process uptimevarnish.cache.mgt.uptime.countUptime in seconds of the management processSecond
Child process startedvarnish.cache.mgt.child_start.countNumber of times the child process has been startedCount
Child process normal exitvarnish.cache.mgt.child_exit.countNumber of times the child process has been cleanly stoppedCount
Child process unexpected exitvarnish.cache.mgt.child_stop.countNumber of times the child process has exited with an unexpected return codeCount
Child process died (signal)varnish.cache.mgt.child_died.countNumber of times the child process has died due to signalsCount
Child process core dumpedvarnish.cache.mgt.child_dump.countNumber of times the child process has produced core dumpsCount
Child process panicvarnish.cache.mgt.child_panic.countNumber of times the management process has caught a child panicCount
Metric nameMetric keyDescriptionUnit
Return codevarnish.cache.returncodeReturn code of the varnishstat commandUnspecified
Metric nameMetric keyDescriptionUnit
Allocator requestsvarnish.cache.smf.c_req.countNumber of times the storage has been asked to provide a storage segment.Count
Allocator failuresvarnish.cache.smf.c_fail.countNumber of times the storage has failed to provide a storage segment.Count
Bytes allocatedvarnish.cache.smf.c_bytes.countNumber of total bytes allocated by this storage.Byte
Bytes freedvarnish.cache.smf.c_freed.countNumber of total bytes returned to this storage.Byte
Allocations outstandingvarnish.cache.smf.g_allocNumber of storage allocations outstanding.Count
Bytes outstandingvarnish.cache.smf.g_bytesNumber of bytes allocated from the storage.Byte
Bytes availablevarnish.cache.smf.g_spaceNumber of bytes left in the storage.Byte
N struct smfvarnish.cache.smf.g_smfN struct smfCount
N small free smfvarnish.cache.smf.g_smf_fragN small free smfCount
N large free smfvarnish.cache.smf.g_smf_largeN large free smfCount
Metric nameMetric keyDescriptionUnit
Allocator requestsvarnish.cache.smu.c_req.countNumber of times the storage has been asked to provide a storage segment.Count
Allocator failuresvarnish.cache.smu.c_fail.countNumber of times the storage has failed to provide a storage segment.Count
Bytes allocatedvarnish.cache.smu.c_bytes.countNumber of total bytes allocated by this storage.Byte
Bytes freedvarnish.cache.smu.c_freed.countNumber of total bytes returned to this storage.Byte
Allocations outstandingvarnish.cache.smu.g_allocNumber of storage allocations outstanding.Count
Bytes outstandingvarnish.cache.smu.g_bytesNumber of bytes allocated from the storage.Byte
Bytes availablevarnish.cache.smu.g_spaceNumber of bytes left in the storage.Byte
Metric nameMetric keyDescriptionUnit
Allocator requestsvarnish.cache.sma.c_req.countNumber of times the storage has been asked to provide a storage segment.Count
Allocator failuresvarnish.cache.sma.c_fail.countNumber of times the storage has failed to provide a storage segment.Count
Bytes allocatedvarnish.cache.sma.c_bytes.countNumber of total bytes allocated by this storage.Byte
Bytes freedvarnish.cache.sma.c_freed.countNumber of total bytes returned to this storage.Byte
Allocations outstandingvarnish.cache.sma.g_allocNumber of storage allocations outstanding.Count
Bytes outstandingvarnish.cache.sma.g_bytesNumber of bytes allocated from the storage.Byte
Bytes availablevarnish.cache.sma.g_spaceNumber of bytes left in the storage.Byte
Metric nameMetric keyDescriptionUnit
stat summ operationsvarnish.cache.main.summs.countNumber of times per-thread statistics were summed into the global counters.Count
Child process uptimevarnish.cache.main.uptime.countHow long the child process has been running.Second
Sessions acceptedvarnish.cache.main.sess_conn.countCount of sessions successfully acceptedCount
Session accept failuresvarnish.cache.main.sess_fail.countCount of failures to accept TCP connection. This counter is the sum of the sess_fail_* counters, which give more detailed information.Count
Session accept failures: connection abortedvarnish.cache.main.sess_fail_econnaborted.countDetailed reason for sess_fail: Connection aborted by the client, usually harmless.Count
Session accept failures: interrupted system callvarnish.cache.main.sess_fail_eintr.countDetailed reason for sess_fail: The accept() call was interrupted, usually harmlessCount
Session accept failures: too many open filesvarnish.cache.main.sess_fail_emfile.countDetailed reason for sess_fail: No file descriptor was available. Consider raising RLIMIT_NOFILE (see ulimit -n).Count
Session accept failures: bad file descriptorvarnish.cache.main.sess_fail_ebadf.countDetailed reason for sess_fail: The listen socket file descriptor was invalid. Should never happen.Count
Session accept failures: not enough memoryvarnish.cache.main.sess_fail_enomem.countDetailed reason for sess_fail: Most likely insufficient socket buffer memory. Should never happenCount
Session accept failures: othervarnish.cache.main.sess_fail_other.countDetailed reason for sess_fail: neither of the above, see SessError log (varnishlog -g raw -i SessError).Count
Client requests received, subject to 400 errorsvarnish.cache.main.client_req_400.count400 means we couldn't make sense of the request, it was malformed in some drastic way.Count
Client requests received, subject to 417 errorsvarnish.cache.main.client_req_417.count417 means that something went wrong with an Expect: header.Count
Good client requests receivedvarnish.cache.main.client_req.countThe count of parseable client requests seen.Count
ESI subrequestsvarnish.cache.main.esi_req.countNumber of ESI subrequests made.Count
Cache hitsvarnish.cache.main.cache_hit.countCount of cache hits. A cache hit indicates that an object has been delivered to a client without fetching it from a backend server.Count
Cache grace hitsvarnish.cache.main.cache_hit_grace.countCount of cache hits with grace. A cache hit with grace is a cache hit where the object is expired. Note that such hits are also included in the cache_hit counter.Count
Cache hits for pass.varnish.cache.main.cache_hitpass.countCount of hits for pass. A cache hit for pass indicates that Varnish is going to pass the request to the backend and this decision has been cached in it self. This counts how many times the cached decision is being used.Count
Cache hits for miss.varnish.cache.main.cache_hitmiss.countCount of hits for miss. A cache hit for miss indicates that Varnish is going to proceed as for a cache miss without request coalescing, and this decision has been cached. This counts how many times the cached decision is being used.Count
Cache missesvarnish.cache.main.cache_miss.countCount of misses. A cache miss indicates the object was fetched from the backend before delivering it to the client.Count
Uncacheable backend responsesvarnish.cache.main.beresp_uncacheable.countCount of backend responses considered uncacheable.Count
Shortlived objectsvarnish.cache.main.beresp_shortlived.countCount of objects created with ttl+grace+keep shorter than the 'shortlived' runtime parameter.Count
Backend conn. successvarnish.cache.main.backend_conn.countHow many backend connections have successfully been established.Count
Backend conn. not attemptedvarnish.cache.main.backend_unhealthy.countBackend conn. not attemptedCount
Backend conn. too manyvarnish.cache.main.backend_busy.countBackend conn. too manyCount
Backend conn. failuresvarnish.cache.main.backend_fail.countBackend conn. failuresCount
Backend conn. reusesvarnish.cache.main.backend_reuse.countCount of backend connection reuses. This counter is increased whenever we reuse a recycled connection.Count
Backend conn. recyclesvarnish.cache.main.backend_recycle.countCount of backend connection recycles. This counter is increased whenever we have a keep-alive connection that is put back into the pool of connections. It has not yet been used, but it might be, unless the backend closes it.Count
Backend conn. retryvarnish.cache.main.backend_retry.countBackend conn. retryCount
Fetch no body (HEAD)varnish.cache.main.fetch_head.countberesp with no body because the request is HEAD.Count
Fetch with Lengthvarnish.cache.main.fetch_length.countberesp.body with Content-Length.Count
Fetch chunkedvarnish.cache.main.fetch_chunked.countberesp.body with Chunked.Count
Fetch EOFvarnish.cache.main.fetch_eof.countberesp.body with EOF.Count
Fetch bad T-Evarnish.cache.main.fetch_bad.countberesp.body length/fetch could not be determined.Count
Fetch no bodyvarnish.cache.main.fetch_none.countberesp.body emptyCount
Fetch no body (1xx)varnish.cache.main.fetch_1xx.countberesp with no body because of 1XX response.Count
Fetch no body (204)varnish.cache.main.fetch_204.countberesp with no body because of 204 response.Count
Fetch no body (304)varnish.cache.main.fetch_304.countberesp with no body because of 304 response.Count
Fetch failed (all causes)varnish.cache.main.fetch_failed.countberesp fetch failed.Count
Background fetch failed (no thread)varnish.cache.main.bgfetch_no_thread.countA bgfetch triggered by a grace hit failed, no thread available.Count
Number of thread poolsvarnish.cache.main.poolsNumber of thread pools. See also parameter thread_pools. NB: Presently pools cannot be removed once created.Count
Total number of threadsvarnish.cache.main.threadsNumber of threads in all pools. See also parameters thread_pools, thread_pool_min and thread_pool_max.Count
Threads hit maxvarnish.cache.main.threads_limited.countNumber of times more threads were needed, but limit was reached in a thread pool. See also parameter thread_pool_max.Count
Threads createdvarnish.cache.main.threads_created.countTotal number of threads created in all pools.Count
Threads destroyedvarnish.cache.main.threads_destroyed.countTotal number of threads destroyed in all pools.Count
Thread creation failedvarnish.cache.main.threads_failed.countNumber of times creating a thread failed. See VSL::Debug for diagnostics. See also parameter thread_fail_delay.Count
Length of session queuevarnish.cache.main.thread_queue_lenLength of session queue waiting for threads. NB: Only updates once per second. See also parameter thread_queue_limit.Count
Number of requests sent to sleep on busy objhdrvarnish.cache.main.busy_sleep.countNumber of requests sent to sleep without a worker thread because they found a busy object.Count
Number of requests woken after sleep on busy objhdrvarnish.cache.main.busy_wakeup.countNumber of requests taken off the busy object sleep list and rescheduled.Count
Number of requests killed after sleep on busy objhdrvarnish.cache.main.busy_killed.countNumber of requests killed from the busy object sleep list due to lack of resources.Count
Sessions queued for threadvarnish.cache.main.sess_queued.countNumber of times session was queued waiting for a thread. See also parameter thread_queue_limit.Count
Sessions dropped for threadvarnish.cache.main.sess_dropped.countNumber of times an HTTP/1 session was dropped because the queue was too long already. See also parameter thread_queue_limit.Count
Requests droppedvarnish.cache.main.req_dropped.countNumber of times an HTTP/2 stream was refused because the queue was too long already. See also parameter thread_queue_limit.Count
object structs madevarnish.cache.main.n_objectApproximate number of HTTP objects (headers + body, if present) in the cache.Count
unresurrected objectsvarnish.cache.main.n_vampireobjectNumber of unresurrected objectsCount
objectcore structs madevarnish.cache.main.n_objectcoreApproximate number of object metadata elements in the cache. Each object needs an objectcore, extra objectcores are for hit-for-miss, hit-for-pass and busy objects.Count
objecthead structs madevarnish.cache.main.n_objectheadApproximate number of different hash entries in the cache.Count
Number of backendsvarnish.cache.main.n_backendNumber of backends known to us.Count
Number of expired objectsvarnish.cache.main.n_expired.countNumber of objects that expired from cache because of old age.Count
Number of LRU nuked objectsvarnish.cache.main.n_lru_nuked.countHow many objects have been forcefully evicted from storage to make room for a new object.Count
Number of LRU moved objectsvarnish.cache.main.n_lru_moved.countNumber of move operations done on the LRU list.Count
Reached nuke_limitvarnish.cache.main.n_lru_limited.countNumber of times more storage space were needed, but limit was reached in a nuke_limit. See also parameter nuke_limit.Count
HTTP header overflowsvarnish.cache.main.losthdr.countHTTP header overflowsCount
Total sessions seenvarnish.cache.main.s_sess.countTotal sessions seenCount
Number of ongoing pipe sessionsvarnish.cache.main.n_pipeNumber of ongoing pipe sessionsCount
Pipes hit pipe_sess_maxvarnish.cache.main.pipe_limited.countNumber of times more pipes were needed, but the limit was reached. See also parameter pipe_sess_max.Count
Total pipe sessions seenvarnish.cache.main.s_pipe.countTotal pipe sessions seenCount
Total pass-ed requests seenvarnish.cache.main.s_pass.countTotal pass-ed requests seenCount
Total backend fetches initiatedvarnish.cache.main.s_fetch.countTotal backend fetches initiated, including background fetches.Count
Total backend background fetches initiatedvarnish.cache.main.s_bgfetch.countTotal backend background fetches initiatedCount
Total synthetic responses madevarnish.cache.main.s_synth.countTotal synthetic responses madeCount
Request header bytesvarnish.cache.main.s_req_hdrbytes.countTotal request header bytes receivedByte
Request body bytesvarnish.cache.main.s_req_bodybytes.countTotal request body bytes receivedByte
Response header bytesvarnish.cache.main.s_resp_hdrbytes.countTotal response header bytes transmittedByte
Response body bytesvarnish.cache.main.s_resp_bodybytes.countTotal response body bytes transmittedByte
Pipe request header bytesvarnish.cache.main.s_pipe_hdrbytes.countTotal request bytes received for piped sessionsByte
Piped bytes from clientvarnish.cache.main.s_pipe_in.countTotal number of bytes forwarded from clients in pipe sessionsByte
Piped bytes to clientvarnish.cache.main.s_pipe_out.countTotal number of bytes forwarded to clients in pipe sessionsByte
Session Closedvarnish.cache.main.sess_closed.countSession ClosedCount
Session Closed with errorvarnish.cache.main.sess_closed_err.countTotal number of sessions closed with errors. See sc_* diag counters for detailed breakdownCount
Session Read Aheadvarnish.cache.main.sess_readahead.countSession Read AheadCount
Session herdvarnish.cache.main.sess_herd.countNumber of times the timeout_linger triggeredCount
Session OK REM_CLOSEvarnish.cache.main.sc_rem_close.countNumber of session closes with REM_CLOSE (Client Closed)Count
Session OK REQ_CLOSEvarnish.cache.main.sc_req_close.countNumber of session closes with REQ_CLOSE (Client requested close)Count
Session Err REQ_HTTP10varnish.cache.main.sc_req_http10.countNumber of session closes with Error REQ_HTTP10 (Proto < HTTP/1.1)Count
Session Err RX_BADvarnish.cache.main.sc_rx_bad.countNumber of session closes with Error RX_BAD (Received bad req/resp)Count
Session Err RX_BODYvarnish.cache.main.sc_rx_body.countNumber of session closes with Error RX_BODY (Failure receiving req.body)Count
Session Err RX_JUNKvarnish.cache.main.sc_rx_junk.countNumber of session closes with Error RX_JUNK (Received junk data)Count
Session Err RX_OVERFLOWvarnish.cache.main.sc_rx_overflow.countNumber of session closes with Error RX_OVERFLOW (Received buffer overflow)Count
Session Err RX_TIMEOUTvarnish.cache.main.sc_rx_timeout.countNumber of session closes with Error RX_TIMEOUT (Receive timeout)Count
Session Err RX_CLOSE_IDLEvarnish.cache.main.sc_rx_close_idle.countNumber of session closes with Error RX_CLOSE_IDLE: timeout_idle has been exceeded while waiting for a client request.Count
Session OK TX_PIPEvarnish.cache.main.sc_tx_pipe.countNumber of session closes with TX_PIPE (Piped transaction)Count
Session Err TX_ERRORvarnish.cache.main.sc_tx_error.countNumber of session closes with Error TX_ERROR (Error transaction)Count
Session OK TX_EOFvarnish.cache.main.sc_tx_eof.countNumber of session closes with TX_EOF (EOF transmission)Count
Session OK RESP_CLOSEvarnish.cache.main.sc_resp_close.countNumber of session closes with RESP_CLOSE (Backend/VCL requested close)Count
Session Err OVERLOADvarnish.cache.main.sc_overload.countNumber of session closes with Error OVERLOAD (Out of some resource)Count
Session Err PIPE_OVERFLOWvarnish.cache.main.sc_pipe_overflow.countNumber of session closes with Error PIPE_OVERFLOW (Session pipe overflow)Count
Session Err RANGE_SHORTvarnish.cache.main.sc_range_short.countNumber of session closes with Error RANGE_SHORT (Insufficient data for range)Count
Session Err REQ_HTTP20varnish.cache.main.sc_req_http20.countNumber of session closes with Error REQ_HTTP20 (HTTP2 not accepted)Count
Session Err VCL_FAILUREvarnish.cache.main.sc_vcl_failure.countNumber of session closes with Error VCL_FAILURE (VCL failure)Count
Delivery failed due to insufficient workspace.varnish.cache.main.client_resp_500.countNumber of times we failed a response due to running out of workspace memory during delivery.Count
workspace_backend overflowsvarnish.cache.main.ws_backend_overflow.countNumber of times we ran out of space in workspace_backend.Count
workspace_client overflowsvarnish.cache.main.ws_client_overflow.countNumber of times we ran out of space in workspace_client.Count
workspace_thread overflowsvarnish.cache.main.ws_thread_overflow.countNumber of times we ran out of space in workspace_thread.Count
workspace_session overflowsvarnish.cache.main.ws_session_overflow.countNumber of times we ran out of space in workspace_session.Count
SHM recordsvarnish.cache.main.shm_records.countNumber of log records written to the shared memory log.Count
SHM writesvarnish.cache.main.shm_writes.countNumber of individual writes to the shared memory log. A single write may batch multiple records for bufferred tasks.Count
SHM flushes due to overflowvarnish.cache.main.shm_flushes.countNumber of writes performed before the end of a bufferred task because adding a record to a batch would exceed vsl_buffer.Count
SHM lock contentionvarnish.cache.main.shm_cont.countNumber of times a write had to wait for the lock.Count
SHM cycles through VSL spacevarnish.cache.main.shm_cycles.countNumber of times a write of log records would reach past the end of the shared memory log, cycling back to the beginning.Count
SHM bytesvarnish.cache.main.shm_bytes.countNumber of bytes written to the shared memory log.Byte
Backend requests madevarnish.cache.main.backend_req.countBackend requests madeCount
Number of loaded VCLs in totalvarnish.cache.main.n_vclNumber of loaded VCLs in totalCount
Number of VCLs availablevarnish.cache.main.n_vcl_availNumber of VCLs availableCount
Number of discarded VCLsvarnish.cache.main.n_vcl_discardNumber of discarded VCLsCount
VCL failuresvarnish.cache.main.vcl_fail.countCount of failures which prevented VCL from completing.Count
Count of bansvarnish.cache.main.bansNumber of all bans in system, including bans superseded by newer bans and bans already checked by the ban-lurker.Count
Number of bans marked 'completed'varnish.cache.main.bans_completedNumber of bans which are no longer active, either because they got checked by the ban-lurker or superseded by newer identical bans.Count
Number of bans using obj.*varnish.cache.main.bans_objNumber of bans which use obj.* variables. These bans can possibly be washed by the ban-lurker.Count
Number of bans using req.*varnish.cache.main.bans_reqNumber of bans which use req.* variables. These bans can not be washed by the ban-lurker.Count
Bans addedvarnish.cache.main.bans_added.countCounter of bans added to ban list.Count
Bans deletedvarnish.cache.main.bans_deleted.countCounter of bans deleted from ban list.Count
Bans tested against objects (lookup)varnish.cache.main.bans_tested.countCount of how many bans and objects have been tested against each other during hash lookup.Count
Objects killed by bans (lookup)varnish.cache.main.bans_obj_killed.countNumber of objects killed by bans during object lookup.Count
Bans tested against objects (lurker)varnish.cache.main.bans_lurker_tested.countCount of how many bans and objects have been tested against each other by the ban-lurker.Count
Ban tests tested against objects (lookup)varnish.cache.main.bans_tests_tested.countCount of how many tests and objects have been tested against each other during lookup. 'ban req.url == foo && req.http.host == bar' counts as one in 'bans_tested' and as two in 'bans_tests_tested'Count
Ban tests tested against objects (lurker)varnish.cache.main.bans_lurker_tests_tested.countCount of how many tests and objects have been tested against each other by the ban-lurker. 'ban req.url == foo && req.http.host == bar' counts as one in 'bans_tested' and as two in 'bans_tests_tested'Count
Objects killed by bans (lurker)varnish.cache.main.bans_lurker_obj_killed.countNumber of objects killed by the ban-lurker.Count
Objects killed by bans for cutoff (lurker)varnish.cache.main.bans_lurker_obj_killed_cutoff.countNumber of objects killed by the ban-lurker to keep the number of bans below ban_cutoff.Count
Bans superseded by other bansvarnish.cache.main.bans_dups.countCount of bans replaced by later identical bans.Count
Lurker gave way for lookupvarnish.cache.main.bans_lurker_contention.countNumber of times the ban-lurker had to wait for lookups.Count
Bytes used by the persisted ban listsvarnish.cache.main.bans_persisted_bytesNumber of bytes used by the persisted ban lists.Byte
Extra bytes in persisted ban lists due to fragmentationvarnish.cache.main.bans_persisted_fragmentationNumber of extra bytes accumulated through dropped and completed bans in the persistent ban lists.Byte
Number of purge operations executedvarnish.cache.main.n_purges.countNumber of purge operations executedCount
Number of purged objectsvarnish.cache.main.n_obj_purged.countNumber of purged objectsCount
Number of objects mailed to expiry threadvarnish.cache.main.exp_mailed.countNumber of objects mailed to expiry thread for handling.Count
Number of objects received by expiry threadvarnish.cache.main.exp_received.countNumber of objects received by expiry thread for handling.Count
HCB Lookups without lockvarnish.cache.main.hcb_nolock.countHCB Lookups without lockCount
HCB Lookups with lockvarnish.cache.main.hcb_lock.countHCB Lookups with lockCount
HCB Insertsvarnish.cache.main.hcb_insert.countHCB InsertsCount
ESI parse errors (unlock)varnish.cache.main.esi_errors.countESI parse errors (unlock)Count
ESI parse warnings (unlock)varnish.cache.main.esi_warnings.countESI parse warnings (unlock)Count
Loaded VMODsvarnish.cache.main.vmodsLoaded VMODsCount
Gzip operationsvarnish.cache.main.n_gzip.countGzip operationsCount
Gunzip operationsvarnish.cache.main.n_gunzip.countGunzip operationsCount
Test gunzip operationsvarnish.cache.main.n_test_gunzip.countThose operations occur when Varnish receives a compressed object from a backend. They are done to verify the gzip stream while it's inserted in storage.Count
Premature iovec flushesvarnish.cache.main.http1_iovs_flush.countNumber of additional writes performed on HTTP1 connections because the number of IO vectors was too small to submit all possible IO in one go. This number is configured through the http1_iovs parameter for client connections and implicitly defined by the amount of free workspace for backend connections.Count

Full version history

To have more information on how to install the downloaded package, please follow the instructions on this page.
ReleaseDate

Full version history

⚠️ Important Change:

  • This version requires a minimum Dynatrace version of 1.345.0

New in this release

  • This extension is now using all rich visualization features of Grail within Infrastructure & Operations App.
  • More metrics for broader monitoring.
  • Varnish cache is relocated under Network category within Infrastructure & Operations App

Full version history

Fixed in this version:

  • Addressed an issue where the extension was not collecting metrics for Varnish plus/enterprise varnishstat binaries.

Full version history

WARNING: Possible breaking changes and warnings - PLEASE READ before upgrading:

  • This version requires a minimum Dynatrace version of 1.338.0 and a minimum OneAgent version of 1.318.0
  • This version includes a breaking change for Dynatrace on Grail.
    • You must opt-in to OpenPipeline configuration via Settings API – see the documentation.

New in this version:

  • Smartscape 2.0 nodes and edges on Grail.

Full version history

New in this version:

  • Add support for python 3.14

Improvements in this version:

  • Update recommended feature sets

Full version history

✨ New in this version:

  • Added additional binary verification for increased security

Full version history

✨ New in this version:

  • Update entity links on gen 3 dashboard to link to I&O app

Full version history

⚠️ WARNING: This version introduces a breaking change requiring the monitoring configuration to be updated

  • The Path to varnishstat executable field must no longer contain the varnishstat binary in it, but only the path to the directory containing the executable with a trailing slash
    • i.e. /usr/bin/

🐛 Bugs fixed:

  • Improved filtering for command path execution to prevent any injection vulnerability.
Dynatrace Hub
Get data into DynatraceBuild your own app
Dynatrace Intelligence - The Agentic PlatformThe Dynatrace Agentic AI ecosystem
All (954)Log Management and AnalyticsKubernetesAI and LLM ObservabilityInfrastructure ObservabilitySoftware DeliveryApplication ObservabilityApplication SecurityBusiness ObservabilityDigital Experience
Filter
Type
Built and maintained by
Partner FinderBecome a partnerDynatrace Developer

Discover recent additions to Dynatrace

Arize AX logo

Arize AX

Analyze traces, latency, and evals of LLM apps through Arize OpenInference data.

AI Observability logo

AI Observability

End-to-end observability for your Agentic AI and LLM workloads.

Dynatrace Assist logo

Dynatrace Assist

Dynatrace Assist: Ask, analyze, and act with Dynatrace Intelligence.

SRE Agent logo

SRE Agent

Analyze and triage incidents.

Smartscape logo

Smartscape

Interactively explore and analyze topology and relationships in digital systems.

Clouds logo

Clouds

Gain full visibility and proactive monitoring across your cloud infrastructure.

Analyze your data

Understand your data better with deep insights and clear visualizations.

Notebooks logo

Notebooks

Create powerful, data-driven documents for custom analytics and collaboration.

Dashboards logo

Dashboards

Transform complex data into clear visualizations with custom dashboards.

Investigations logo

Investigations

Fast and precise incident response on Grail data with DQL queries.

Smartscape logo

Smartscape

Interactively explore and analyze topology and relationships in digital systems.

Logs logo

Logs

Explore all your logs without writing a single query.

Problems logo

Problems

Detect, explain and triage problems automatically using Dynatrace Intelligence.

Automate your processes

Turn data and answers into actions, securely, and at scale.

Workflows logo

Workflows

Automate tasks in your IT landscape and move towards autonomous operations.

Jira logo

Jira

Open, update, and close Jira tickets automatically from Dynatrace Workflows.

Slack logo

Slack

Automate Slack messaging for security incidents, attacks, remediation, and more.

Secure your cloud application

See vulnerabilities and attacks in your environment.

Security Posture Management logo

Security Posture Management

Detect, prioritize, and remediate security and compliance findings with SPM.

Threats & Exploits logo

Threats & Exploits

Understand, triage, and investigate detection findings and alerts.

More resources

Cursor (Live-Debugger) logo

Cursor (Live-Debugger)

Get Real time Code-Level data directly to your Cursor IDE.

Documents logo

Documents

Manage Dashboards, Notebooks and other documents in your Dynatrace environment.

GitHub Copilot Coding Agent logo

GitHub Copilot Coding Agent

Automate vulnerability remediation and boost developer productivity.

GitHub Copilot Custom Agent logo

GitHub Copilot Custom Agent

Automate your development workflows with specialized agent definitions.

Dynatrace Live Debugger on JetBrains logo

Dynatrace Live Debugger on JetBrains

Get real-time code-level data directly to your Jetbrains IDE.

Metrics logo

Metrics

Browse, search, and manage all your metrics in one central catalog.

Dynatrace Live Debugger on Windsurf logo

Dynatrace Live Debugger on Windsurf

Get real-time code-level data directly to your Windsurf IDE.

Are you looking for something different?

We have hundreds of apps, extensions, and other technologies to customize your environment

Leverage our newest innovations of Dynatrace Saas

Kick-start your app creation

Kick-start your app creation

Whether you’re a beginner or a pro, Dynatrace Developer has the tools and support you need to create incredible apps with minimal effort.
Go to Dynatrace Developer
Upgrading from Dynatrace Managed to SaaS

Upgrading from Dynatrace Managed to SaaS

Drive innovation, speed, and agility in your organization by seamlessly and securely upgrading.
Learn More
Log Management and Analytics

Log Management and Analytics

Innovate faster and more efficiently with unified log management and log analytics for actionable insights and automation.
Learn more