Custom Analyics not working from 12.7.0

@MaxCloutier Are they change in custom analytics we should know about in 12.7.0. Am trying to implement the old custom analytics and am getting these errors


03/19/2020 12:35:02.457 Launcher ========================================
                                             Botpress Server
                                              Version 12.7.1
                                                 OS win32
03/19/2020 12:35:02.460 Launcher App Data Dir: "C:\Users\Michael.Mukwekezeke\botpress"
03/19/2020 12:35:13.297 Launcher Using 10 modules
                        ⦿ analytics
                        ⦿ basic-skills
                        ⦿ builtin
                        ⦿ channel-web
                        ⦿ code-editor
                        ⦿ examples
                        ⦿ extensions
                        ⦿ nlu
                        ⦿ qna
                        ⦿ testing
                        ⊝ channel-messenger (disabled)
                        ⊝ channel-slack (disabled)
                        ⊝ channel-smooch (disabled)
                        ⊝ channel-teams (disabled)
                        ⊝ channel-telegram (disabled)
                        ⊝ hitl (disabled)
                        ⊝ misunderstood (disabled)
                        ⊝ nlu-extras (disabled)
                        ⊝ nlu-testing (disabled)
                        ⊝ uipath (disabled)
03/19/2020 12:35:13.298 Server Running in DEVELOPMENT MODE
03/19/2020 12:35:19.588 Server Loaded 10 modules
03/19/2020 12:35:19.689 CMS Loaded 7 content types
03/19/2020 12:35:20.852 HTTP External URL is not configured. Using default value of http://localhost:3000. Some features may not work properly
03/19/2020 12:35:20.853 Server Discovered 0 bots
03/19/2020 12:35:20.858 Server Started in 7560ms
03/19/2020 12:35:20.858 Launcher Botpress is listening at: http://localhost:3000
03/19/2020 12:35:20.858 Launcher Botpress is exposed at: http://localhost:3000
03/19/2020 12:39:01.783  2020-03-19T10:39:01.783Z bp:dialog (test) [w-8dtihHrv9etQniOvcn] init new context { currentNode: 'node-fc39', currentFlow: 'main.flow.json' }{ botId: 'test' }
03/19/2020 12:39:01.784  2020-03-19T10:39:01.784Z bp:dialog (test) [w-8dtihHrv9etQniOvcn] execute action "analytics/set"{ botId: 'test' }
03/19/2020 12:39:01.803 ActionService An error occurred while executing the action "analytics/set
                             HTTP (post) URL http://localhost:3000/api/v1/bots/test/mod/analytics/custom_metrics/set
                             Received "<!DOCTYPE html>
                             <html lang="en">
                             <meta charset="utf-8">
                             < (...)"
                             Request failed with status code 404
Error: Request failed with status code 404
    at createError (C:\snapshot\build-windows\node_modules\axios\lib\core\createError.js:16:15)
    at settle (C:\snapshot\build-windows\node_modules\axios\lib\core\settle.js:17:12)
    at IncomingMessage.handleStreamEnd (C:\snapshot\build-windows\node_modules\axios\lib\adapters\http.js:237:11)
    at IncomingMessage.emit (events.js:187:15)
    at IncomingMessage.EventEmitter.emit (domain.js:442:20)
    at endReadableNT (_stream_readable.js:1081:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
03/19/2020 12:39:01.805  2020-03-19T10:39:01.805Z bp:dialog (test) [w-8dtihHrv9etQniOvcn] transit (main.flow.json) [node-fc39] >> (error.flow.json) [entry]{ botId: 'test' }
03/19/2020 12:39:01.806  2020-03-19T10:39:01.806Z bp:dialog (test) [w-8dtihHrv9etQniOvcn] render element "#!builtin_text-error"{ botId: 'test' }
03/19/2020 12:39:01.810  2020-03-19T10:39:01.810Z bp:dialog (test) [w-8dtihHrv9etQniOvcn] ending flow{ botId: 'test' }

this is the flow

Hey @DigiSenseiZim

I am sorry for that confusion. We’ve removed custom analytics and replaced it by a more standard set of metrics. We want to provide a better out of the box analytics and we plan on bringing back custom eventually if it’s a requested feature. For now, we believe the new analytics will fit the needs of the community.

Feel free to reach out if you want to talk about this in details.


Aight cool saw the PR. I personally love custom metrics but I suppose I will have to resort to chucking stuff in the database then pulling it all out using a separate analytics tool. (Checking which product was most viewed / which queries are trending / which interactions are most popular / where people come from and so on.)

The “most used workflows” would have sufficed but then flow styling is different per developer and when you wanna breakdown the task there aint no leeway to consider how the analytics will appear (For instance you would have re-usable flows for validations, repeated API Calls filling common slots and so on)

My loudest cry is that I would have to refactor 14+ bots to keep up to date with the current binaries which I am definitely not gonna do so I will play around with the old analytics.tgz and see if it works with the new versions. If not I will stick to making new stuff only on the new binaries.

Thanks for the prompt reply!