Greg Stephens
Greg Stephens
This is somewhat related to #9013. Running `rasa shell --debug` is a workaround to see the actual entity extraction failure.
@ancalita do you know if this will be merged into the next 3.2.x release?
Closing this. Rebasing on `3.2.x` and opening #11436.
yes, thanks for the reminder
> Before I give the final approval, asked a clarifying question on a docs sentence. Also please add a unit test if possible, that the metadata gets added to the...
Closing. Rebased to `3.2.x` and replaced by PR #11435
Exalate commented: rgstephens commented: Yes, there's currently work on this which you can find in the Rasa [open-telemetry](https://github.com/RasaHQ/rasa/tree/open-telemetry) branch and there's also an example action server in the Sara/Rasa Demo...
Exalate commented: rgstephens commented: You should be using it as part of either the standard [docker-compose](https://rasa.com/docs/rasa-x/installation-and-setup/install/docker-compose) setup either of the Kubernetes based installs - [quick start](https://rasa.com/docs/rasa-x/installation-and-setup/install/quick-install-script) which uses k3s or...
Exalate commented: rgstephens commented: Would be good to add accepting of injected context from front end. Both rest and sockets.
Exalate commented: rgstephens commented: I built an updated [image](https://hub.docker.com/r/stephens/rasa-otel) of `2.8.1` with OpenTracing/Jaeger and also sanic-prometheus. If anyone used the older image, the `endpoints.yml` values have changed. See the image...