https://signoz.io logo
Join the conversationJoin Slack
Channels
contributing
contributing-frontend
general
github-activities
incidents
k8s_operator_helm
reactjs-config
signoz-alert-testing
support
testsupport
watercooler
webhook-dev
write-for-signoz
Powered by Linen
support
  • v

    Vishal Sharma

    09/16/2022, 9:19 AM
    Please follow this tutorial:
    a
    a
    • 3
    • 21
  • r

    Rahul Tiwari

    09/16/2022, 9:55 AM
    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.
    • 1
    • 1
  • p

    Prakshal Shah

    09/16/2022, 9:56 AM
    Is it possible to have a server of SigNoz(outside of Kubernetes) and Kubernetes should share tracing data to SigNoz?
    n
    • 2
    • 3
  • d

    Dam Mad

    09/16/2022, 10:39 AM
    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?
    a
    • 2
    • 5
  • s

    sudhanshu dev

    09/16/2022, 10:53 AM
    @nitya-signoz Getting this error in signoz otel-collector pods. 2022-09-16T10:50:13.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-16T10:50:24.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-16T10:50:43.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-16T10:51:03.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-16T10:51:43.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-16T10:52:43.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"}
    p
    a
    • 3
    • 2
  • a

    Alejandro Decchi

    09/16/2022, 12:49 PM
    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 ?
    s
    p
    • 3
    • 19
  • s

    Sudarsanam Krishnan

    09/16/2022, 12:52 PM
    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?
    s
    • 2
    • 9
  • m

    Mark Moales

    09/16/2022, 2:39 PM
    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!
    s
    • 2
    • 13
  • a

    Alejandro Decchi

    09/16/2022, 8:20 PM
    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.
    s
    • 2
    • 1
  • u

    Upesh Jindal

    09/20/2022, 1:44 AM
    How to get the gunicorn post_work hook working mentioned here: https://signoz.io/docs/instrumentation/python/?utm_source=instrumentation_page&amp;utm_medium=frontend&amp;utm_term=language#running-applic[…]gunicorn-uwsgi
    s
    • 2
    • 6
  • u

    Upesh Jindal

    09/20/2022, 1:44 AM
    Getting this message: Overriding of current TracerProvider is not allowed
  • u

    Upesh Jindal

    09/20/2022, 1:44 AM
    I picked up the example mentioned on the link above
  • s

    sudhanshu dev

    09/20/2022, 11:13 AM
    @Prashant Shahi @nitya-signoz Getting below error in click house pod
  • s

    sudhanshu dev

    09/20/2022, 11:13 AM
    2022.09.20 11:07:20.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::Net::SocketImpl::error(int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x1b3e3efb in /usr/bin/clickhouse 2. Poco::Net::SecureSocketImpl::handleError(int) @ 0x1b395612 in /usr/bin/clickhouse 3. Poco::Net::SecureSocketImpl::sendBytes(void const*, int, int) @ 0x1b3966ee in /usr/bin/clickhouse 4. Poco::Net::HTTPClientSession::write(char const*, long) @ 0x1b3b36fd in /usr/bin/clickhouse 5. Poco::Net::HTTPFixedLengthStreamBuf::writeToDevice(char const*, long) @ 0x1b3b6c50 in /usr/bin/clickhouse 6. Poco::Net::HTTPFixedLengthIOS::~HTTPFixedLengthIOS() @ 0x1b3b6e9b in /usr/bin/clickhouse 7. non-virtual thunk to Poco::Net::HTTPFixedLengthOutputStream::~HTTPFixedLengthOutputStream() @ 0x1b3b7b22 in /usr/bin/clickhouse 8. Poco::Net::HTTPClientSession::receiveResponse(Poco::Net::HTTPResponse&) @ 0x1b3b1c91 in /usr/bin/clickhouse 9. DB::S3:😛ocoHTTPClient::makeRequestInternal(Aws::Http::HttpRequest&, std::__1:😒hared_ptr&lt;DB::S3::PocoHTTPResponse>&, Aws::Utils::RateLimits::RateLimiterInterface*, Aws::Utils::RateLimits::RateLimiterInterface*) const @ 0x15123566 in /usr/bin/clickhouse 10. DB::S3:😛ocoHTTPClient::MakeRequest(std::__1:😒hared_ptr&lt;Aws::Http::HttpRequest> const&, Aws::Utils::RateLimits::RateLimiterInterface*, Aws::Utils::RateLimits::RateLimiterInterface*) const @ 0x15121c49 in /usr/bin/clickhouse 11. Aws::Client::AWSClient::AttemptOneRequest(std::__1:😒hared_ptr&lt;Aws::Http::HttpRequest> const&, Aws::AmazonWebServiceRequest const&, char const*, char const*, char const*) const @ 0x1b614447 in /usr/bin/clickhouse 12. Aws::Client::AWSClient::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::Client::AWSXMLClient::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::S3::S3Client::UploadPart(Aws::S3::Model::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::__1::thread&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 11:07:20.079762 [ 645 ] {} <Error> AWSClient: HTTP response code: -1
  • s

    sudhanshu dev

    09/20/2022, 11:14 AM
    bcz of this our query-service pods in crash back loop
    s
    n
    +2
    • 5
    • 40
  • s

    sudhanshu dev

    09/20/2022, 11:14 AM
    but no error in query service logs
  • s

    sudhanshu dev

    09/20/2022, 11:14 AM
    any idea
  • s

    sudhanshu dev

    09/20/2022, 11:14 AM
    it showing the AWS CLI issue
  • r

    Rahul Tiwari

    09/21/2022, 7:28 AM
    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
    p
    • 2
    • 5
  • s

    Sudarsanam Krishnan

    09/22/2022, 10:23 AM
    Hi All, I'm new
  • s

    Sudarsanam Krishnan

    09/22/2022, 10:24 AM
    to Signoz. Facing an issue after stopping the services and restarting them
  • s

    Sudarsanam Krishnan

    09/22/2022, 10:24 AM
    sudo docker-compose -f docker/clickhouse-setup/docker-compose.yaml stop ==> Stopped the service
  • s

    Sudarsanam Krishnan

    09/22/2022, 10:29 AM
    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
    p
    • 2
    • 1
  • a

    Adi

    09/23/2022, 3:31 AM
    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?
    a
    • 2
    • 1
  • r

    Richard Howell-Peak

    09/23/2022, 9:36 AM
    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"
    • 1
    • 2
  • a

    Ashish

    09/23/2022, 10:30 AM
    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/
    p
    • 2
    • 1
  • k

    Kapil Yadav

    09/24/2022, 4:20 PM
    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-24T16:15:01Z" 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 16:15:01 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
    p
    p
    • 3
    • 7
  • k

    Kapil Yadav

    09/25/2022, 7:30 AM
    all fixed, except
    p
    • 2
    • 1
  • k

    Kapil Yadav

    09/25/2022, 7:30 AM
    failed to create "clickhousetraces" exporter, in pipeline "traces": error connecting to primary db: dial tcp 10.100.169.191:9000: i/o timeout
    p
    p
    • 3
    • 14
  • k

    Kapil Yadav

    09/25/2022, 7:30 AM
    new error 😄
Powered by Linen
Title
k

Kapil Yadav

09/25/2022, 7:30 AM
new error 😄
View count: 1