A few questions from a newbie

Rasa Open Source
1

Hi all, I’m trying to study Rasa OpenSource and have few questions, that I can’t find answers to anywhere

  1. I switched on postgres tracker. It create only one table named “events”. In the postgres broker manual says that it create the same table. Is it ok, or my tracker configured wrong?

  2. I tried to find some open source tools for viewing sessions and users dialogue history, but it looks like all these projects a died. Rasa X not free so does really, none of the users need to debug and monitor their bots?

  3. What is the best way to store DB connections requisite for rasa custom actions? In the examples i could find requisites hardcodet directly in the custom actions function. This doesn’t seem to be the best way. Not to mention that the connection will be opened every time the action is called.

  4. I tried to find some alternate rasa actions sdk, but all of them seems as died and didn’t develop for 6 years :frowning: As I understand it, this is the main way to integrate race with other systems, but there are no libraries or examples anywhere.

In general, it seemed to me that the open community of Rasa had died since the RasaX become non free, since most of the articles and projects on Github dated back to the period before the closure.

2 Likes
2

  1. Rasa will create the table, you shouldn’t need to do this

  2. I don’t know of any active open source projects for this. Many people export the data to spreadsheets or other tools. For export, you have 3 approaches: (1) scrape the rasa log with debug; (2) capture events using the event broker feature; (3) export from your tracker db

  3. You can find some examples here that use python classes to keep api/db connections open.

  4. If you don’t want to use python and the std rasa-sdk then you’ll have a good amount of work to duplicate this yourself. As you said, there are old projects in JavaScript, Java & Go that I am aware of but I don’t think any are actively maintained or update for 3.x

1 Like
3

Thank you very much for your answer, Greg!