MAUs reporting built-in solution.

It is the case, for the client requesting this solution, as well as for many other clients that are moving Watson Assistant instances to production that they do not have a built in solution to get the MAU value for a specific month.

Context: Caixa is one of the biggest clients for IBM in the region of SPGI. They are currently making use of a Watson Assistant instance in production, that has been deployed over Cloud Pak for Data on IBM Cloud (ROKs). IBM asks for them to provide the MAU value for the correct reporting of WA usage on a monthly basis. However this is the current solution that is provided by IBM:

It is the client's job to develop a script in charge of downloading, storing and processing the conversational logs for each of the Watson Assistant instances they are using. After this, they can calculate the correct MAU value and report it back to IBM. After talking with the product team, we discovered that other clients are: "parsing logs or capturing end users to identify unique ids."

This is not an acceptable enterprise solution for large scale WA customers and should have been present in the first version of the WA service.

We have developed a script, but it has been taken by the client as a temporal solution. The script, if the logs are downloaded in blocks of 10,000, causes watson metrics pods to crash, which can be very dangerous for productive environments and has caused problems in the current Caixa Bank environment. On the other hand, if the block size is decreased then the solution is not scalable given that it takes too much time.

What do we require? A built-in solution for MAUs calculation, i.e. a capability in ROKs that outputs the MAU value for a specific month. As explained by the product team this capability: "may come in the future but right now there is no timeline to deliver it.". We need to roll out this solution as soon as possible, now that more and more clients are starting to roll out productive WA instances. It may seem a small problem now, but it sure will explode.

A case has also been opened to solved this issue: TS014256336.