fleandro flga

## test.odin
package main

import "core:fmt"
import "core:runtime"
import "core:time"

PATH_NODE_LEN :: 64

PathNode :: struct {
	len:     int,

## caddy_metrics.md

      
        
          
            
              
              1 file
            
          
          
            
              
              0 forks
            
          
          
            
              
              0 comments
            
          
          
            
              
              1 star
            
          
        
        
          
              
          
          
            
                flga
                / caddy_metrics.md
            
            
              Last active
              September 22, 2022 00:16
            
              
                caddy metrics proposal
              
          
        
      
        
  
      
    I've been reading the metrics related issues and I must admit it's a little hard to follow.
Performance and metric quality #4644

We instrument every handler in the chain, this is both expensive and at the same time not that useful for complex setups.
As someone who recently had to configure metrics and dashboards for a caddy instance I was underwhelmed.
The core issue (for me) is that a handler's metrics don't provide much value. On one hand, as was mentioned before, with deep chains they tend to be very redundant, on the other, they're not granular enough - I can see I'm serving N qps on file_server, but, which one?
I posit that there are 2 main use cases for http metrics:
	package main

	import "core:fmt"
	import "core:runtime"
	import "core:time"

	PATH_NODE_LEN :: 64

	PathNode :: struct {
	len: int,