Error on request for user_agent table

[reynlds]

Upgrade DAP to 3.9.1 today in order to take advantage of the 2 new tables delivered on the canvas_logs schema as of yesterday's update. However, the user_agent table is not available:

"The table name 'user_agent' specified in the request is not valid. (2a66e171-2160-4e9a-9e23-966dbdfd99d7)"

"dap.dap_error.NotFoundError"

[mclark19 · Accepted solution]

The user_agents table was deprecated, so there is only web_logs in the canvas_logs namespace currently.

[marco_divittori]

Are you querying the new "canvas_logs" namespace? I'm seeing the new tables today.

 % dap list --namespace canvas_logs                                                                                                                           
user_agents
web_logs

[reynlds]

Yes. The web_logs are received w/o issue. Just not seeing the user_agents. Probably less important, but would still like to capture it.

[marco_divittori]

From the error message you posted it looks like the code is looking for a "user_agent" table (no s) instead of "user_agents" table. Could that be it?

[reynlds]

Yes. The web_logs are received w/o issue. Just not seeing the user_agents. Probably less important, but would still like to capture it.

Also, I realized that earlier I was leaving the "s" off of "user_agents". I resolved that but an issue remains:

0b5f05e8-eae9-4586-8cde-16b3f6a36e9d, KeyError: 'http_user_agent'

[ac1918]

Hello, did you ever figure this out? I just tried requesting the user_agents table and received the following:

"ERROR - An exception occurred while executing the command: The table name 'user_agents' specified in the request is not valid. (51442240-c4ef-4827-9dd6-ee3e51283cd2)"

The request for the web_logs table worked, but not the one for user_agents.

[mclark19 · Accepted solution]

The user_agents table was deprecated, so there is only web_logs in the canvas_logs namespace currently.

[sgergely · Accepted solution]

Hey, user_agents are deprecated and got removed in 2024-11-23. It was announced in 2023-12-16.

[ac1918]

Lol, that certainly explains the error. Thanks!