Vishal Sharma

Results 99 issues of Vishal Sharma

We are using [Clickhouse-go](https://github.com/ClickHouse/clickhouse-go) as client and using `@param` to bind parameters to a query. But in latest version [v2.5.0](https://github.com/ClickHouse/clickhouse-go/releases/tag/v2.5.0) it has moved to native [query parameters](https://clickhouse.com/docs/en/sql-reference/syntax/#defining-and-using-query-parameters) and deprecated `@param`...

query-service

Currently SigNoz supports flamegraph to visualize a single trace. But a serviceMap like visualization of trace can be helpful to visualize route of a request. Eg:

enhancement
trace-detail-page
ideas

Base their access levels based on our AD/SAML groups, and provision the users so we don't have to create them each manually. https://app.intercom.com/a/inbox/wmkurvb7/inbox/shared/all/conversation/6001#part_id=comment-6001-19069 https://app.intercom.com/a/inbox/wmkurvb7/inbox/shared/all/conversation/6124#part_id=initial-part-6124-2716629379

enhancement
enterprise
sso
customer demand
ICP

Loom: https://www.loom.com/share/31520cf739af40fd8b13791efbeb55b4?sid=ce7abbae-ebc3-4d7d-be7b-c1308e70168f

bug
frontend

Currently we are using wrong log levels for query service logs. Eg: using debug level logs where it should have been error level or info level. https://github.com/SigNoz/signoz/blob/82936f73a3720d028f96653bd868b03ad14388da/pkg/query-service/app/clickhouseReader/reader.go#L444

query-service

https://signoz.io/docs/tutorial/opentelemetry-operator-usage/#overview

onboarding

request-more-info
saas-onboarding

Since the method of instrumentation is selected to quick start by default so we need not have different page for the same

saas-onboarding

Add default selection and default name for service names, datasource etc

saas-onboarding

Loom video: https://www.loom.com/share/c26ad18d126948dcadae5059d0898a13?sid=478c7714-44e7-4ae2-8647-5731544cf720

bug
frontend
saas-onboarding