diff --git a/pkg/server/templates/content/tab_reqbuilder.templ b/pkg/server/templates/content/tab_reqbuilder.templ index b1e0464..0ee75f3 100644 --- a/pkg/server/templates/content/tab_reqbuilder.templ +++ b/pkg/server/templates/content/tab_reqbuilder.templ @@ -29,7 +29,7 @@ templ ReqBuilderTab(txsSet vsl.TransactionSet) {

Here you can generate commands with curl and other tools based on parsed VSL transaction tags. For POST/PUT requests, the body is not available in varnishlog and won’t be included.

Here you can generate commands with curl and other tools based on parsed VSL transaction tags. For POST/PUT requests, the body is not available in varnishlog and won’t be included.

Transaction: ") if templ_7745c5c3_Err != nil { return templ_7745c5c3_Err } diff --git a/pkg/server/templates/content/tab_timestamps.templ b/pkg/server/templates/content/tab_timestamps.templ index 0c9693e..f9e7c86 100644 --- a/pkg/server/templates/content/tab_timestamps.templ +++ b/pkg/server/templates/content/tab_timestamps.templ @@ -18,7 +18,7 @@ templ TimestampsTab(txsSet vsl.TransactionSet) {

Generate charts to analyze latencies by parsing VSL timestamps.

If you're focused on analyzing latencies, you can shorten the logs by filtering for the relevant tags. For example:

varnishlog -g request -i Begin,Timestamp,Link,End

You can also add std.timestamp(\"my-label\") entries directly in your VCL to track the timing of specific VCL operations.


Timestamp value:
Timestamp events:
") + _, templ_7745c5c3_Err = templ_7745c5c3_Buffer.WriteString("

Generate charts to analyze latencies by parsing VSL timestamps.

If you're focused on analyzing latencies, you can shorten the logs by filtering for the relevant tags. For example:

varnishlog -g request -i Begin,Timestamp,Link,End

You can also add std.timestamp(\"my-label\") entries directly in your VCL to track the timing of specific VCL operations.


Timestamp value:
Timestamp events:
") if templ_7745c5c3_Err != nil { return templ_7745c5c3_Err }