- 🇪🇸Spain rodrigoaguilera Barcelona
What happened with this?
The current version doesn't seem to have a debug module - 🇨🇦Canada mparker17 UTC-4
@rodrigoaguilera, this happened before I became a maintainer, so I'm not sure exactly.
Looks like it was deleted from the 8.x-5.x branch about a month after it was added...
$ git checkout 8.x-5.x Switched to branch '8.x-5.x' Your branch is up to date with 'origin/8.x-5.x'. $ git log -- 'modules/elasticsearch_connector_devel/elasticsearch_connector_devel.info' commit f33acbf882fe95e63b4f92eebae2f276d8447bf7 Author: Nikolay Ignatov Date: 2014-05-26 23:53:55 +0300 Clearing some 7.x-1.x code and adding some initial yml file. commit 58873ed84103aea8cfa299db2b9c0549ad098e23 Author: Nikolay Ignatov Date: 2014-04-12 12:49:58 +0300 Fixing issue #2218455. Adding a debugger module.
... it also looks like it was never ported to 8.x-6.x or 8.x-7.x...
⋯/elasticsearch_connector on 8.x-5.x via 🐘 $ git checkout 8.x-6.x Switched to branch '8.x-6.x' Your branch is up to date with 'origin/8.x-6.x'. $ git log -- 'modules/elasticsearch_connector_devel/elasticsearch_connector_devel.info' $ git checkout 8.x-7.x Switched to branch '8.x-7.x' Your branch is up to date with 'origin/8.x-7.x'. $ git log -- 'modules/elasticsearch_connector_devel/elasticsearch_connector_devel.info' $
It's not exactly the same, but there is a "Enable debugging mode: log ElasticSearch network traffic" option when you're configuring a server in 8.0.x, which will log information about queries and responses to Drupal's logger mechanism: https://git.drupalcode.org/project/elasticsearch_connector/-/blob/8.0.x/... - see 📌 Logging should be configurable Fixed for more information.
Does this "Enable debugging mode: log ElasticSearch network traffic" option satisfy your needs?
- 🇪🇸Spain rodrigoaguilera Barcelona
I totally missed that checkbox. It doesn't fill my need because it doesn't log the body of the POST request. only this:
Request: POST http://elasticsearch:9200/general/_search?track_total_hits=true
The response is actually complete. This is probably how the original debugging module worked so the current situation is fine.
I'll open a new issue if I need to improve the logging. Thank you so much for looking into this.