Please follow this tutorial:

Hello Team, I was trying to install signoz ver 0.10.2 on my k8s environment, but otel colector is geting installed as deamonset,whereas i want otel collector to be installed as deployment.

Is it possible to have a server of SigNoz(outside of Kubernetes) and Kubernetes should share tracing data to SigNoz?

question: we are monitoring the API, we would like to send heart beats to our

/

endpoint every 1 min to monitor whether API is live. Is it possible to send heartbeats directly from SigNoz or do we need to implement it separately?

@nitya-signoz Getting this error in signoz otel-collector pods. 2022-09-16T105013.984Z info exporterhelper/queued_retry.go:215 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "code: 117, message: Object has ambiguous path: service_instance_id: while executing 'FUNCTION _CAST(labels :: 3, 'Object(\\'json\\')' :: 4) -> _CAST(labels, 'Object(\\'json\\')') Object('json') : 6'", "interval": "262.727993ms"} 2022-09-16T105024.050Z info exporterhelper/queued_retry.go:215 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "code: 117, message: Object has ambiguous path: service_instance_id: while executing 'FUNCTION _CAST(labels :: 3, 'Object(\\'json\\')' :: 4) -> _CAST(labels, 'Object(\\'json\\')') Object('json') : 6'", "interval": "172.174283ms"} 2022-09-16T105043.607Z info exporterhelper/queued_retry.go:215 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "code: 117, message: Object has ambiguous path: service_instance_id: while executing 'FUNCTION _CAST(labels :: 3, 'Object(\\'json\\')' :: 4) -> _CAST(labels, 'Object(\\'json\\')') Object('json') : 6'", "interval": "39.655712ms"} 2022-09-16T105103.954Z info exporterhelper/queued_retry.go:215 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "code: 117, message: Object has ambiguous path: service_instance_id: while executing 'FUNCTION _CAST(labels :: 3, 'Object(\\'json\\')' :: 4) -> _CAST(labels, 'Object(\\'json\\')') Object('json') : 6'", "interval": "26.415154ms"} 2022-09-16T105143.611Z info exporterhelper/queued_retry.go:215 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "code: 117, message: Object has ambiguous path: service_instance_id: while executing 'FUNCTION _CAST(labels :: 3, 'Object(\\'json\\')' :: 4) -> _CAST(labels, 'Object(\\'json\\')') Object('json') : 6'", "interval": "55.362672ms"} 2022-09-16T105243.615Z info exporterhelper/queued_retry.go:215 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "code: 117, message: Object has ambiguous path: service_instance_id: while executing 'FUNCTION _CAST(labels :: 3, 'Object(\\'json\\')' :: 4) -> _CAST(labels, 'Object(\\'json\\')') Object('json') : 6'", "interval": "54.74043ms"}

Hi, I’m using the helm charts to deploy signoz. Signoz version: 0.11.0 Helm chart version: 0.3.3 First, I have some problem running

signoz-query-services

, it constantly restarting. Logs looks ok:

2022-09-16T12:44:52.645Z	INFO	app/server.go:84	Using ClickHouse as datastore ...
ts=2022-09-16T12:44:52.652594487Z caller=log.go:168 level=info msg="Loading configuration file" filename=/root/config/prometheus.yml
2022-09-16T12:44:52.654Z	INFO	alertManager/notifier.go:94	Starting notifier with alert manager:[<http://signoz-alertmanager:9093/api/>]
2022-09-16T12:44:52.654Z	INFO	app/server.go:396	rules manager is ready
ts=2022-09-16T12:44:52.656830443Z caller=log.go:168 level=info msg="Completed loading of configuration file" filename=/root/config/prometheus.yml
2022-09-16T12:44:52.657Z	INFO	alertManager/notifier.go:126	msg: Initiating alert notifier...
2022-09-16T12:44:52.658Z	INFO	app/server.go:273	Query server started listening on 0.0.0.0:8080...
2022-09-16T12:44:52.658Z	INFO	app/server.go:286	Query server started listening on private port 0.0.0.0:8085...
starting private http
2022-09-16T12:44:52.658Z	INFO	app/server.go:312	Starting HTTP server{port 11 8080  <nil>} {addr 15 0 0.0.0.0:8080 <nil>}
2022-09-16T12:44:52.658Z	INFO	app/server.go:324	Starting pprof server{addr 15 0 0.0.0.0:6060 <nil>}
2022-09-16T12:44:52.658Z	INFO	app/server.go:338	Starting Private HTTP server{port 11 8085  <nil>} {addr 15 0 0.0.0.0:8085 <nil>}
2022-09-16T12:44:52.700Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 27.736µs
2022-09-16T12:44:55.562Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 16.782µs
2022-09-16T12:44:55.562Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 14.205µs

Is a way to troubleshoot it ? to put on Debug ? Second, on the other hand, is a way to set

signoz-otel-collector

as deployment in place of daemonset ?

Hello All, New to Signoz. Tried setting up Signoz using Docker Swarm on Windows 11. Stack deployment executed fine. Stack services are looking fine, but running http://localhost:3301 responds with a "Not Found" text alone on the page. Has anyone faced this before?

Hi all, I'm new to SigNoz. I have a gRPC service that I am trying to instrument, and I verified that it is generating telemetry data using both the console exporter and using the OpenTelemetry collector running in Docker Desktop. I stopped the OpenTelemetry collector and installed SigNoz in Docker Desktop. I verified I can access the front end and checked the endpoint using troubleshoot.

~/temp$ ./troubleshoot checkEndpoint --endpoint=localhost:4317
2022-09-16T09:59:00.676-0400    INFO    workspace/main.go:28    STARTING!
2022-09-16T09:59:00.676-0400    INFO    checkEndpoint/checkEndpoint.go:41       checking reachability of SigNoz endpoint
2022-09-16T09:59:00.681-0400    INFO    workspace/main.go:46    Successfully sent sample data to signoz ...

The problem is I am not seeing any data being captured in SigNoz when I hit my gRPC service. When I start the service, I have the OTEL_EXPORTER_OTLP_ENDPOINT environment variable set to http://localhost:4317. We use auto instrumentation using the following code:

resource = Resource(attributes={"service.name": service_name})
trace.set_tracer_provider(TracerProvider(resource=resource))
trace.get_tracer_provider().add_span_processor(
    BatchSpanProcessor(OTLPSpanExporter()))
LoggingInstrumentor().instrument(set_logging_format=True)
GrpcInstrumentorServer().instrument()

Any ideas? Thanks!

Hi, Is a way to calculate the amount of resources needed by Signoz Collector, some of them are restarted by OOM. I could find a link where give me an idea of memory, cpu to run in k8s.

How to get the gunicorn post_work hook working mentioned here: https://signoz.io/docs/instrumentation/python/?utm_source=instrumentation_page&utm_medium=frontend&utm_term=language#running-applic[…]gunicorn-uwsgi

Getting this message: Overriding of current TracerProvider is not allowed

I picked up the example mentioned on the link above

@Prashant Shahi @nitya-signoz Getting below error in click house pod

2022.09.20 110720.079564 [ 645 ] {} <Error> AWSClient: Failed to make request to: https://signoz-cold-storage.s3.amazonaws.com/data/naivunrtrexkiklvgiwdjopkkswwbroq?partNumber=1&amp;uploadId=BUEate2QiDWOGtv3U4tx7UpKuge7VDiw7oKMLBj7gtx7Kjvj7Vc8l0nmkmaGrPtaenddYX77lvd7lm6BKNEZStrdBE46KQGIc7dyD7clUqKvqtEy79itTbUHQ22VB0dTpxlJvnOGcWwKYzC7eSonLRSFmF1f9I53NiAhs7on5zx3u1cPvRo4qegR2SR2ghrF: Poco::Exception. Code: 1000, e.code() = 32, I/O error: Broken pipe, Stack trace (when copying this message, always include the lines below): 0. Poco:IOException:IOException(std: 1:basic_string<char, std: 1:char_traits<char>, std: 1:allocator<char> > const&, int) @ 0x1b54e38c in /usr/bin/clickhouse 1. Poco:NetSocketImpl:error(int, std: 1:basic_string<char, std: 1:char_traits<char>, std: 1:allocator<char> > const&) @ 0x1b3e3efb in /usr/bin/clickhouse 2. Poco:NetSecureSocketImpl:handleError(int) @ 0x1b395612 in /usr/bin/clickhouse 3. Poco:NetSecureSocketImpl:sendBytes(void const*, int, int) @ 0x1b3966ee in /usr/bin/clickhouse 4. Poco:NetHTTPClientSession:write(char const*, long) @ 0x1b3b36fd in /usr/bin/clickhouse 5. Poco:NetHTTPFixedLengthStreamBuf:writeToDevice(char const*, long) @ 0x1b3b6c50 in /usr/bin/clickhouse 6. Poco:NetHTTPFixedLengthIOS:~HTTPFixedLengthIOS() @ 0x1b3b6e9b in /usr/bin/clickhouse 7. non-virtual thunk to Poco:NetHTTPFixedLengthOutputStream:~HTTPFixedLengthOutputStream() @ 0x1b3b7b22 in /usr/bin/clickhouse 8. Poco:NetHTTPClientSession:receiveResponse(Poco:Net:HTTPResponse&) @ 0x1b3b1c91 in /usr/bin/clickhouse 9. DB:S3PocoHTTPClient:makeRequestInternal(Aws:Http:HttpRequest&, std: 1shared ptr&lt;DBS3:PocoHTTPResponse>&, Aws:UtilsRateLimits:RateLimiterInterface*, Aws:UtilsRateLimits:RateLimiterInterface*) const @ 0x15123566 in /usr/bin/clickhouse 10. DB:S3PocoHTTPClient:MakeRequest(std: 1shared ptr&lt;AwsHttp:HttpRequest> const&, Aws:UtilsRateLimits:RateLimiterInterface*, Aws:UtilsRateLimits:RateLimiterInterface*) const @ 0x15121c49 in /usr/bin/clickhouse 11. Aws:ClientAWSClient:AttemptOneRequest(std: 1shared ptr&lt;AwsHttp:HttpRequest> const&, Aws::AmazonWebServiceRequest const&, char const*, char const*, char const*) const @ 0x1b614447 in /usr/bin/clickhouse 12. Aws:ClientAWSClient:AttemptExhaustively(Aws:Http:URI const&, Aws::AmazonWebServiceRequest const&, Aws:Http:HttpMethod, char const*, char const*, char const*) const @ 0x1b61155e in /usr/bin/clickhouse 13. Aws:ClientAWSXMLClient:MakeRequest(Aws:Http:URI const&, Aws::AmazonWebServiceRequest const&, Aws:Http:HttpMethod, char const*, char const*, char const*) const @ 0x1b61ea6d in /usr/bin/clickhouse 14. Aws:S3S3Client:UploadPart(Aws:S3Model:UploadPartRequest const&) const @ 0x1b733623 in /usr/bin/clickhouse 15. DB:WriteBufferFromS3:processUploadRequest(DB:WriteBufferFromS3:UploadPartTask&) @ 0x15a087b2 in /usr/bin/clickhouse 16. ? @ 0x15a0a3e0 in /usr/bin/clickhouse 17. ? @ 0x16456be0 in /usr/bin/clickhouse 18. ThreadPoolImpl<ThreadFromGlobalPool>::worker(std: 1:__list_iterator<ThreadFromGlobalPool, void*>) @ 0xb7aa77a in /usr/bin/clickhouse 19. ThreadFromGlobalPool::ThreadFromGlobalPool<void ThreadPoolImpl<ThreadFromGlobalPool>::scheduleImpl<void>(std: 1:function<void ()>, int, std: 1:optional<unsigned long>)::'lambda0'()>(void&&)::'lambda'()::operator()() @ 0xb7ac764 in /usr/bin/clickhouse 20. ThreadPoolImpl<std: 1thread&gt;:worker(std: 1 list iterator&lt;std 1:thread, void*>) @ 0xb7a7ba7 in /usr/bin/clickhouse 21. ? @ 0xb7ab5dd in /usr/bin/clickhouse 22. ? @ 0x7fdbbf623609 in ? 23. __clone @ 0x7fdbbf548163 in ? (version 22.4.5.9 (official build)) 2022.09.20 110720.079762 [ 645 ] {} <Error> AWSClient: HTTP response code: -1

bcz of this our query-service pods in crash back loop

but no error in query service logs

any idea

it showing the AWS CLI issue

Hello Team, I want to update my pv and pvc of clickhouse.persistence.size from 20GB to 100GB, i have also followed the below command but it is also updating my signoz from v0.10.2 to the latest version but i don't want to update my signoz version as such. kubectl patch storageclass gp2 -p '{"allowVolumeExpansion": true}' helm -n platform upgrade my-release signoz/signoz --set clickhouse.persistence.size=100Gi

Hi All, I'm new

to Signoz. Facing an issue after stopping the services and restarting them

sudo docker-compose -f docker/clickhouse-setup/docker-compose.yaml stop ==> Stopped the service

sudo docker-compose -f docker/clickhouse-setup/docker-compose.yaml up --> kept on throwing error with redis time out. But I got this fixed by redeploying again, with a d flag added

Hi everyone, I wanna ask about how to implement SigNoz on vue js? Is there any documentation about how to implement SigNoz on vue js?

I'm trying to implement my own metrics endpoint to show a time-series of values. I've successfully created my own prometheus format exporter, and signoz is configured to pull that data in. When I omit the timestamps from the prometheus format (so it looks like this:

name {} 3.0

then I get a horizontal line, so no time-series, just one value only. Then I put the timestamps in, like this:

name {} 3.0 1663923600

for example, then it successfully imports but when I try and create the dashboard it says "no data available"

I am facing issue in configuring my reactjs application for monitoring using Signow, even the default application is not working, can anyone guide me how to fix the issue. I followed this documentation - https://signoz.io/blog/opentelemetry-react/

New to Signoz, was installing to EKS using helm facing below issue from one of the issue: signoz-playground-dev-otel-collector-694d5dd67d-75x69: time="2022-09-24T161501Z" level=info msg="Executing:\nCREATE DATABASE IF NOT EXISTS signoz_metrics\n" component=clickhouse signoz-playground-dev-otel-collector-694d5dd67d-75x69: Error: cannot build pipelines: failed to create "clickhouselogsexporter" exporter, in pipeline "logs": cannot configure clickhouse logs exporter: code: 516, message: admin: Authentication failed: password is incorrect or there is no user with such name signoz-playground-dev-otel-collector-694d5dd67d-75x69: 2022/09/24 161501 application run finished with error: cannot build pipelines: failed to create "clickhouselogsexporter" exporter, in pipeline "logs": cannot configure clickhouse logs exporter: code: 516, message: admin: Authentication failed: password is incorrect or there is no user with such name

all fixed, except

failed to create "clickhousetraces" exporter, in pipeline "traces": error connecting to primary db: dial tcp 10.100.169.1919000 i/o timeout

new error 😄