Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analytics tab internal error #618

Closed
AesSedai opened this issue Mar 10, 2024 · 5 comments · Fixed by #669
Closed

Analytics tab internal error #618

AesSedai opened this issue Mar 10, 2024 · 5 comments · Fixed by #669
Assignees
Labels
awaiting investigation The issue has been assigned to a team member for investigation. bug Something isn't working internally-reviewed The issue has been reviewed internally.

Comments

@AesSedai
Copy link

Component(s)

studio

Component version

0.70.4

wgc version

0.44.2

controlplane version

0.74.1

router version

0.72.0

What happened?

If possible, please create a PR with a failing test to illustrate the issue clearly.
Otherwise, please attach a minimum reproduction through a GitHub repository that includes
essential information such as the relevant subgraph SDLs.
Please also make sure that the instructions for the reproduction are clear, tested, and fully accurate.

Description

The Studio Analytics tab and traces tab show an internal server error when loading their pages

Steps to Reproduce

Run the "Local Development" steps in the readme
Make a request in the Studio -> Playground tab
Navigate to the Studio -> Analytics tab, select Traces
=> Could not retrieve analytics data, [internal] internal error

Expected Result

Studio -> Analytics tab should show Traces

Actual Result

Studio -> Analytics tab shows an error

image

Environment information

Environment

OS: WSL2 Ubuntu 20.04.5 LTS
Package Manager: pnpm: 8.15.4, nodejs: v20.11.1
Compiler(if manually compiled): go version go1.22.1 linux/amd64

Router configuration

Default "Local Development" setup

Router execution config

Default "Local Development" setup

Log output

[23:28:53 UTC] INFO: incoming request {"reqId":"req-cq","req":{"method":"GET","url":"/wg.cosmo.platform.v1.PlatformService/GetAnalyticsView?connect=v1&encoding=json&message=%7B%22federatedGraphName%22%3A%22mygraph%22%2C%22config%22%3A%7B%22range%22%3A24%2C%22filters%22%3A%5B%7B%22field%22%3A%22operationName%22%2C%22value%22%3A%22MyQuery%22%7D%2C%7B%22field%22%3A%22operationHash%22%2C%22value%22%3A%2215855461482066297239%22%7D%5D%2C%22pagination%22%3A%7B%22limit%22%3A20%7D%2C%22sort%22%3A%7B%22id%22%3A%22unixTimestamp%22%2C%22desc%22%3Atrue%7D%7D%2C%22namespace%22%3A%22default%22%7D","hostname":"localhost:3001","remoteAddress":"127.0.0.1","remotePort":41634}}
[23:28:53 UTC] ERROR: Code: 352. DB::Exception: Block structure mismatch in (columns with identical name must have identical structure) stream: different types:
OrganizationID String String(size = 0)
OrganizationID LowCardinality(String) ColumnLowCardinality(size = 0, UInt8(size = 0), ColumnUnique(size = 1, String(size = 1))). (AMBIGUOUS_COLUMN_NAME) (version 24.2.1.2248 (official build))

[23:28:53 UTC] ERROR: {"reqId":"req-cq","service":"wg.cosmo.platform.v1.PlatformService","method":"GetAnalyticsView","actor":{"userId":"a75303d7-df64-4c64-b25b-847431a1621d","organizationId":"9be50f06-abc7-43ed-a2e2-01ede212677d"}}
[23:28:53 UTC] INFO: request completed {"reqId":"req-cq","res":{"statusCode":500},"responseTime":13.653982043266296}
[23:28:53 UTC] ERROR: Code: 352. DB::Exception: Block structure mismatch in (columns with identical name must have identical structure) stream: different types:
OrganizationID String String(size = 0)
OrganizationID LowCardinality(String) ColumnLowCardinality(size = 0, UInt8(size = 0), ColumnUnique(size = 1, String(size = 1))). (AMBIGUOUS_COLUMN_NAME) (version 24.2.1.2248 (official build))

Additional context

No response

@AesSedai AesSedai added the bug Something isn't working label Mar 10, 2024
Copy link

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible.
The roadmap is driven by our customers and we have to prioritize issues that are important to them.
You can influence the priority by becoming a customer. Please contact us here.

@AesSedai
Copy link
Author

This also shows up as missing info for the Top 10 Operations and Requests sections in the graph overview page:
image

[23:35:08 UTC] INFO: incoming request {"reqId":"req-en","req":{"method":"GET","url":"/wg.cosmo.platform.v1.PlatformService/GetDashboardAnalyticsView?connect=v1&encoding=json&message=%7B%22federatedGraphName%22%3A%22mygraph%22%2C%22range%22%3A4%2C%22namespace%22%3A%22default%22%7D","hostname":"localhost:3001","remoteAddress":"127.0.0.1","remotePort":45800}}
[23:35:08 UTC] ERROR: Code: 352. DB::Exception: Block structure mismatch in (columns with identical name must have identical structure) stream: different types:
SubgraphID LowCardinality(String) ColumnLowCardinality(size = 0, UInt8(size = 0), ColumnUnique(size = 1, String(size = 1)))
SubgraphID String String(size = 0). (AMBIGUOUS_COLUMN_NAME) (version 24.2.1.2248 (official build))

[23:35:08 UTC] ERROR: {"reqId":"req-en","service":"wg.cosmo.platform.v1.PlatformService","method":"GetDashboardAnalyticsView","actor":{"userId":"a75303d7-df64-4c64-b25b-847431a1621d","organizationId":"9be50f06-abc7-43ed-a2e2-01ede212677d"}}
[23:35:08 UTC] INFO: request completed {"reqId":"req-en","res":{"statusCode":500},"responseTime":19.40735900402069}
[23:35:08 UTC] ERROR: Code: 352. DB::Exception: Block structure mismatch in (columns with identical name must have identical structure) stream: different types:
SubgraphID LowCardinality(String) ColumnLowCardinality(size = 0, UInt8(size = 0), ColumnUnique(size = 1, String(size = 1)))
SubgraphID String String(size = 0). (AMBIGUOUS_COLUMN_NAME) (version 24.2.1.2248 (official build))

@StarpTech StarpTech added internally-reviewed The issue has been reviewed internally. awaiting investigation The issue has been assigned to a team member for investigation. labels Mar 11, 2024
@StarpTech
Copy link
Contributor

Hi @AesSedai, thanks for reporting. We will look into it.

@thisisnithin
Copy link
Member

Hi @AesSedai, seems we are having this issue from ClickHouse version 24.2 onwards. While we work on a fix, please use version <= 24.1.

@thisisnithin
Copy link
Member

This is fixed in the latest version of clickhouse. Please reopen if this occurs again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting investigation The issue has been assigned to a team member for investigation. bug Something isn't working internally-reviewed The issue has been reviewed internally.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants