I just upgraded my signoz deployment using the latest helm chart. It looks like I've lost all my previously collected application telemetry. Is that normal?

Hi Team, I have created a VIEWER user (version 0.11.1) and got to the invite link. When filling in the password the "Get Started" Button is grayed out and non clickable. I tried creating another VIEWER user and got the same issue. any suggestion?

@Dudu Bistrov You need to enter the same exact password in the

Password

and

Confirm Password

fields Do ensure that there are no spaces etc

@Pranay when passwords don't match I get a detailed message. Once I copy paste the same exact string from one filed to the other it goes away but the button is still grayed out:

@Nagamani Sakhinana, a SigNoz community member is facing this issue with the go-gin app instrumentation following our blogpost written by @Vishal Sharma, any support will be appreciated.

Hi, Is there anyone to help me out?

Hey, I just updated to v0.12.0 and get following errors on the frontend:

"GET /api/v1/featureFlags HTTP/1.1" 404
"GET /api/v1/version HTTP/1.1" 404
"GET /api/v1/configs HTTP/1.1" 404

this breaks the frontend

will revert to previous version in the meantime UPDATE: I completely re-installed the signoz server, all good now. Maybe the update to the new version didn't go cleanly as docker compose didn't update everything correctly. Not sure.

Hello, I'm seeing a specific service in the services tab and its active and recieving traffic but when I go to service map this service isn't there. Are there any limits to what can be shown in the service map?

Could any of you please clarify 1. How can we Setup for Play Application as play applications are not deployed as jar file- any documentation will be helpful 2. Does Signoz support business logic level metrics and in business layer if we get exception how can we integrate with alerts- for example when an exception occurs in code does Signoz- any guidance documentation alert. 3. Installing Signoz on ECS- any guidance notes would be greatly appreciated

Hi all , I wanted to increase my pvc for clickhouse(datastore) but when i increased it got stuck in terminating state. Please help here

Small thing, but signoz user creation has a bug with email addresses containing a

+

in the name.

I created a first user with an email similar to

<mailto:devops+signoz@somecompany.com|devops+signoz@somecompany.com>

, it logged me in fine. But when logging out and trying to login again, it comes back with a "user not found"

even though it was created exactly like that in the sqlite3 db

Another update regarding 0.12.0: I experienced an instability of the query-service a few more times. After bringing up the docker compose stack (default one minus the hotrod app), the api consistently returns a 404 like mentioned above. Bringing down docker compose and up again fixes the problem.

Currently not 100% sure if it is my environment or a problem with the compose file

It's just weird that bringing the stack down and up again fixes the problem.

I know, it's not much to work on, just throwing it out there in case you observed similar behaviors.

Hello Support Team - We have upgraded Signoz to latest version(0.12.0) but after that we are facing some issue with "No data to display" for any dashboards randomly if we refresh it multiple time then it will start to appear data but from other dashboards data will be showing as "No data to display".

hi! having trouble w/ the upgrade:

signoz-otel-collector 2022-12-16T01:23:53.343Z    info    components/components.go:30    Stability level of component is undefined    {"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "stability": "Undefined"}                                                       │
│ signoz-otel-collector 2022-12-16T01:23:53.454Z    info    clickhousetracesexporter/clickhouse_factory.go:122    View does not exist, skipping patch    {"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "table": "dependency_graph_minutes_db_calls_mv"}               │
│ signoz-otel-collector 2022-12-16T01:23:53.454Z    info    clickhousetracesexporter/clickhouse_factory.go:96    Running migrations from path:     {"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "test": "/migrations"}                                               │
│ signoz-otel-collector 2022-12-16T01:23:53.465Z    info    clickhousetracesexporter/clickhouse_factory.go:108    Clickhouse Migrate finished    {"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "error": "Dirty database version 10. Fix and force version."}          │
│ signoz-otel-collector Error: cannot build pipelines: failed to create "clickhousetraces" exporter, in pipeline "traces": code: 60, message: Table signoz_traces.distributed_signoz_index_v2 doesn't exist                                                                                     │
│ signoz-otel-collector 2022/12/16 01:23:53 application run finished with error: cannot build pipelines: failed to create "clickhousetraces" exporter, in pipeline "traces": code: 60, message: Table signoz_traces.distributed_signoz_index_v2 doesn't exist

any idea how i can get rid of this? i don't have any clickhouse queries on my dashboard or alerts.

Hi! I am new to SigNoz, we have our product stack deployed on eks of different aws accounts of customers. Our dev team would like to have logs of all deployments on a single SigNoz. What is the best way to achieve this, can SigNoz alone support this or we have to use fluentd and/or fluentbit with SigNoz

how to filter by tags in dashboard? Its posible?

Is possible to set SigNoz Clickhouse password as k8s secrets in place to hardcode it in the values.yaml ?

Hello team, I am following the signoz documentation and trying to instrument the Ruby on Rails app. However, My app is failing to start with the error below.

OpenTelemetry error: Unable to export 9 span

(Edit to add logs) Hi, I am having trouble with setting up signoz on a microk8s cluster here is the value file (nothing much, just connect to the external chi)

clickhouse:
  enabled: false

externalClickhouse:
  host: chendpoint-clickhouse.warehouse.svc.cluster.local
  cluster: warehouse
  user: admin
  password: password
  existingSecret: clickhouse-credentials
  existingSecretPasswordKey: admin-password

Now if I install chart 0.5.1,

otel-collector

backoff with

signoz_traces.signoz_index_v2 doesn't exist

error:

2022-12-19T09:19:19.741Z info service/telemetry.go:110 Setting up own telemetry...
2022-12-19T09:19:19.741Z info service/telemetry.go:140 Serving Prometheus metrics {"address": "0.0.0.0:8888", "level": "basic"}
2022-12-19T09:19:19.741Z info components/components.go:30 Stability level of component is undefined {"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "stability": "undefined"}
2022-12-19T09:19:19.745Z info clickhousetracesexporter/clickhouse_factory.go:82 Running migrations from path:  {"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "test": "/migrations"}
2022-12-19T09:19:19.751Z info clickhousetracesexporter/clickhouse_factory.go:94 Clickhouse Migrate finished {"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "error": "no change"}
Error: cannot build pipelines: failed to create "clickhousetraces" exporter, in pipeline "traces": code: 60, message: Table signoz_traces.signoz_index_v2 doesn't exist
2022/12/19 09:19:19 application run finished with error: cannot build pipelines: failed to create "clickhousetraces" exporter, in pipeline "traces": code: 60, message: Table signoz_traces.signoz_index_v2 doesn't exist

Show tables from the

signoz_traces

databases return only

durationSort

otel-collector-metrics

run fine, db and tables are created normally. If I install chart 0.6.0,

otel-collector

and

otel-collector-metrics

crashed immediately with the seg fault errors:

2022-12-19T09:27:25.730Z info service/telemetry.go:111 Setting up own telemetry...
2022-12-19T09:27:25.730Z info service/telemetry.go:141 Serving Prometheus metrics {"address": "0.0.0.0:8888", "level": "Basic"}
2022-12-19T09:27:25.730Z info components/components.go:30 Stability level of component is undefined {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "stability": "Undefined"}
time="2022-12-19T09:27:25Z" level=info msg="Executing:\nCREATE DATABASE IF NOT EXISTS signoz_metrics ON CLUSTER cluster\n" component=clickhouse
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x3864f79]

goroutine 1 [running]:
<http://github.com/SigNoz/signoz-otel-collector/exporter/clickhousemetricsexporter.NewPrwExporter(0xc000dbaa80|github.com/SigNoz/signoz-otel-collector/exporter/clickhousemetricsexporter.NewPrwExporter(0xc000dbaa80>, {{0xc0003ab6c0, {0x529fd20, 0xc001087e00}, {0x52a7c60, 0x7d3d1a0}, 0x0}, {{0x4934385, 0x15}, {0x4931ce2, ...}, ...}})
 /src/exporter/clickhousemetricsexporter/exporter.go:90 +0x2f9
<http://github.com/SigNoz/signoz-otel-collector/exporter/clickhousemetricsexporter.createMetricsExporter(|github.com/SigNoz/signoz-otel-collector/exporter/clickhousemetricsexporter.createMetricsExporter(>{0x52d8d28, 0xc000080018}, {{0xc0003ab6c0, {0x529fd20, 0xc001087e00}, {0x52a7c60, 0x7d3d1a0}, 0x0}, {{0x4934385, 0x15}, ...}}, ...)
 /src/exporter/clickhousemetricsexporter/factory.go:50 +0x9f
<http://go.opentelemetry.io/collector/component.CreateMetricsExporterFunc.CreateMetricsExporter(...)|go.opentelemetry.io/collector/component.CreateMetricsExporterFunc.CreateMetricsExporter(...)>
 /go/pkg/mod/go.opentelemetry.io/collector/component@v0.66.0/exporter.go:149
<http://go.opentelemetry.io/collector/service/internal/pipelines.createExporter({0x52d8d28|go.opentelemetry.io/collector/service/internal/pipelines.createExporter({0x52d8d28>?, 0xc000080018?}, {{0xc0003ab6c0, {0x529fd20, 0xc001087e00}, {0x52a7c60, 0x7d3d1a0}, 0x0}, {{0x4934385, 0x15}, ...}}, ...)
 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/service/internal/pipelines/pipelines.go:374 +0x269
<http://go.opentelemetry.io/collector/service/internal/pipelines.buildExporter({0x52d8d28|go.opentelemetry.io/collector/service/internal/pipelines.buildExporter({0x52d8d28>, 0xc000080018}, {0xc0003aae70, {0x529fd20, 0xc001087e00}, {0x52a7c60, 0x7d3d1a0}, 0x0}, {{0x4934385, 0x15}, ...}, ...)
 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/service/internal/pipelines/pipelines.go:360 +0x2ec
<http://go.opentelemetry.io/collector/service/internal/pipelines.Build({0x52d8d28|go.opentelemetry.io/collector/service/internal/pipelines.Build({0x52d8d28>, 0xc000080018}, {{0xc0003aae70, {0x529fd20, 0xc001087e00}, {0x52a7c60, 0x7d3d1a0}, 0x0}, {{0x4934385, 0x15}, ...}, ...})
 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/service/internal/pipelines/pipelines.go:243 +0x1a85
<http://go.opentelemetry.io/collector/service.(*service).initExtensionsAndPipeline(0xc001087c80|go.opentelemetry.io/collector/service.(*service).initExtensionsAndPipeline(0xc001087c80>, 0xc001a0f540)
 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/service/service.go:162 +0x2bf
<http://go.opentelemetry.io/collector/service.newService(0xc001347540)|go.opentelemetry.io/collector/service.newService(0xc001347540)>
 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/service/service.go:75 +0x525
<http://go.opentelemetry.io/collector/service.(*Collector).setupConfigurationComponents|go.opentelemetry.io/collector/service.(*Collector).setupConfigurationComponents>(0xc001a0fa88, {0x52d8d28, 0xc000080018})
 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/service/collector.go:149 +0x1db
<http://go.opentelemetry.io/collector/service.(*Collector).Run(0xc001a0fa88|go.opentelemetry.io/collector/service.(*Collector).Run(0xc001a0fa88>, {0x52d8d28, 0xc000080018})
 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/service/collector.go:190 +0x46
<http://go.opentelemetry.io/collector/service.NewCommand.func1(0xc000139200|go.opentelemetry.io/collector/service.NewCommand.func1(0xc000139200>, {0x48fa9ce?, 0x1?, 0x1?})
 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/service/command.go:53 +0x479
<http://github.com/spf13/cobra.(*Command).execute(0xc000139200|github.com/spf13/cobra.(*Command).execute(0xc000139200>, {0xc00006e050, 0x1, 0x1})
 /go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:916 +0x862
<http://github.com/spf13/cobra.(*Command).ExecuteC(0xc000139200)|github.com/spf13/cobra.(*Command).ExecuteC(0xc000139200)>
 /go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044 +0x3bc
<http://github.com/spf13/cobra.(*Command).Execute(...)|github.com/spf13/cobra.(*Command).Execute(...)>
 /go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
main.runInteractive({{0xc000ef79b0, 0xc001500b70, 0xc000ef7dd0, 0xc000ef75f0}, {{0x4934385, 0x15}, {0x4931ce2, 0x15}, {0x48f6f03, 0x6}}, ...})
 /src/cmd/signozcollector/main.go:36 +0x5e
main.run(...)
 /src/cmd/signozcollector/main_others.go:8
main.main()
 /src/cmd/signozcollector/main.go:29 +0x1d8

Any ideas on where to look at ? The external clickhouse is at 22.8 version Thanks

How to get this list of

tags

and

values

in dashboard panel by adding the variable?

How do we add multiple httpchecks? Do I just repeat the entire httpcheck block?

receivers:
  httpcheck:
    endpoint: <http://example.com>
    method: GET
    collection_interval: 10s

Hi , few of my applications are deploying successfully and are visible in signoz console but few are deploying successfully but not visible in signoz console

Hello, i was wondering if there is a way to create a dashboard of aggregate trace data