Somehow this error is not explicit, I thought that sysctl was involved in this matter but it was clearly logstash's input's buffer.

input {
    udp {
        type => "netflow"
        port => 5555
        codec => netflow {
            versions => [5]
        }
        workers => 8
        receive_buffer_bytes => 2129920
        queue_size => 200000
    }
}

has fixed it

add_field => [ "[geoip][coordinates]", "%{[geoip][longitude]}" ]
add_field => [ "[geoip][coordinates]", "%{[geoip][latitude]}" ]

à la recherche d'un gif "time machine", je tombe par hasard sur un espèce de shortclip qui contient un perso de the office, en creusant, je découvre cette "perle"

statistics-channels {
inet 127.0.0.1 port 8080 allow { 127.0.0.1; };
};

la version python pour comparer

Les interfaces en go c'est vraiment pas simple ... Pour citer l'article :

Go’s interfaces are one of it’s best features, but they’re also one of the most confusing for newbies.

mais l'exemple est assez parlant :

type Walker interface {
    Walk(miles int)
}

type Camel struct {
    Name string
}

func (c Camel) Walk(miles int) {
     fmt.Printf(“%s is walking %v miles\n”, c.Name, miles)
}

func LongWalk(w Walker) {
     w.Walk(500)
     w.Walk(500)
}

func main() {
    c := Camel{“Bill”}
    LongWalk(c)
}

// prints
// Bill is walking 500 miles.
// Bill is walking 500 miles.

TIL pgbouncer