Hello, the http log plugin is a “request logger” - for each request/response pair that goes through Kong, the plugin makes an http request.
If you have only configured the plugin but made no requests through Kong, the plugin will be installed, but it will never activate. You need to make some traffic go through Kong in order for it to appear in your mockbin instances.
Maybe the traffic you are generating is not triggering the plugin.
First, make sure that the traffic you are generating goes through Kong (not directly to the upstream server)
Also, check that the traffic matches the service 23380fd8-5a4a-4969-b2da-ab477dd1edfb, which is the one associated with your http-log plugin. You must send your request to a route associated to that service.
Check that you are getting the expected responses from your traffic.
Give a look at the nginx logs and see if there are any errors happening while the traffic goes though Kong.
I added the plugin to be global so it should be activated by any services.
But now I think about using StatsD plugin instead of the Http Log.
It may be more useful in my case.
But I don’t understand how to use it.
I receive an error in my logs : send() failed (111: Connection refused) […] statsd_logger.lua:71: send_statsd(): failed to send data to localhost:8125: connection refused
I suppose that is because localhost:8125 is not a StatsD server but I am not sure about that.
And if it is for this reason I would like to know if there is an StatsD online to test it instead of installing one.
The connection refused message seems to indicate that localhost:8125 is not available at all - your problem seems to be network-related more than protocol-related.