SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

SigNoz Community

Hi <@U044Y6A3FMK> You can share your issue with <@U026KJNMVP1>

Hi <@U044Y6A3FMK> you need to run signoz app exporter

<https://signoz.io/blog/opentelemetry-react/|https://signoz.io/blog/opentelemetry-react/>

Can you please confirm whether you have performed all the steps

Today and tomorrow we have holiday also i am not near my laptop

Hi <@U044Y6A3FMK>
Is your query resolved ?

Please let us know when can can we connect regarding this issue

As tracing not working for us in our react.js configuration

Hi <@U026KJNMVP1> Are you available today

<@U02SS3ZAMKQ> <@U043243QEPK> is not able to connect from AWS-hosted Signoz to local running sample react app though app is throwing connection refused error

<@U043243QEPK> can you please share your otel-collector config?

Here is the config <@U02SS3ZAMKQ> -
receivers:
  filelog/dockercontainers:
    include: [  "/var/lib/docker/containers/*/*.log" ]
    start_at: end
    include_file_path: true
    include_file_name: false
    operators:
    - type: json_parser
      id: parser-docker
      output: extract_metadata_from_filepath
      timestamp:
        parse_from: attributes.time
        layout: '%Y-%m-%dT%H:%M:%S.%LZ'
    - type: regex_parser
      id: extract_metadata_from_filepath
      regex: '^.*containers/(?P&lt;container_id&gt;[^_]+)/.*log$'
      parse_from: attributes["log.file.path"]
      output: parse_body
    - type: move
      id: parse_body
      from: attributes.log
      to: body
      output: time
    - type: remove
      id: time
      field: attributes.time
  opencensus:
    endpoint: 0.0.0.0:55678
  otlp/spanmetrics:
    protocols:
      grpc:
        endpoint: localhost:12345
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
      http:
        endpoint: 0.0.0.0:4318
        cors:
          allowed_origins:
           - <https://app.3dcerts.tech>  # URL of your Frontend application
           - <https://admin.3dcerts.tech>
           - <http://admin.3dcerts.tech>
           - <https://validation.3dcerts.tech>
           - <https://app.3dcerts.tech/react>
           - <http://172.31.52.68:3000>
           - <http://103.212.147.18:3000>
           - <http://10.8.0.3:3000>
           - <http://172.19.0.1:3000>
           - <http://10.8.0.1:3000>
  jaeger:
    protocols:
      grpc:
        endpoint: 0.0.0.0:14250
      thrift_http:
        endpoint: 0.0.0.0:14268
      # thrift_compact:
      #   endpoint: 0.0.0.0:6831
      # thrift_binary:
      #   endpoint: 0.0.0.0:6832
  hostmetrics:
    collection_interval: 60s
    scrapers:
      cpu: {}
      load: {}
      memory: {}
      disk: {}
      filesystem: {}
      network: {}

processors:
  batch:
    send_batch_size: 10000
    send_batch_max_size: 11000
    timeout: 10s
  signozspanmetrics/prometheus:
    metrics_exporter: prometheus
    latency_histogram_buckets: [100us, 1ms, 2ms, 6ms, 10ms, 50ms, 100ms, 250ms, 500ms, 1000ms, 1400ms, 2000ms, 5s, 10s, 20s, 40s, 60s ]
    dimensions_cache_size: 10000
    dimensions:
      - name: service.namespace
        default: default
      - name: deployment.environment
        default: default
  # memory_limiter:
  #   # 80% of maximum memory up to 2G
  #   limit_mib: 1500
  #   # 25% of limit up to 2G
  #   spike_limit_mib: 512
  #   check_interval: 5s
  #
  #   # 50% of the maximum memory
  #   limit_percentage: 50
  #   # 20% of max memory usage spike expected
  #   spike_limit_percentage: 20
  # queued_retry:
  #   num_workers: 4
  #   queue_size: 100
  #   retry_on_failure: true
  resourcedetection:
    # Using OTEL_RESOURCE_ATTRIBUTES envvar, env detector adds custom labels.
    detectors: [env, system] # include ec2 for AWS, gce for GCP and azure for Azure.
    timeout: 2s
    override: false

extensions:
  health_check:
    endpoint: 0.0.0.0:13133
  zpages:
    endpoint: 0.0.0.0:55679
  pprof:
    endpoint: 0.0.0.0:1777

exporters:
  clickhousetraces:
    datasource: <tcp://clickhouse:9000/?database=signoz_traces>
  clickhousemetricswrite:
    endpoint: <tcp://clickhouse:9000/?database=signoz_metrics>
    resource_to_telemetry_conversion:
      enabled: true
  prometheus:
    endpoint: 0.0.0.0:8889
  # logging: {}

  clickhouselogsexporter:
    dsn: <tcp://clickhouse:9000/>
    timeout: 5s
    sending_queue:
      queue_size: 100
    retry_on_failure:
      enabled: true
      initial_interval: 5s
      max_interval: 30s
      max_elapsed_time: 300s

service:
  telemetry:
    metrics:
      address: 0.0.0.0:8888
  extensions:
    - health_check
    - zpages
    - pprof
  pipelines:
    traces:
      receivers: [jaeger, otlp]
      processors: [signozspanmetrics/prometheus, batch]
      exporters: [clickhousetraces]
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [clickhousemetricswrite]
    metrics/hostmetrics:
      receivers: [hostmetrics]
      processors: [resourcedetection, batch]
      exporters: [clickhousemetricswrite]
    metrics/spanmetrics:
      receivers: [otlp/spanmetrics]
      exporters: [prometheus]
    logs:
      receivers: [otlp, filelog/dockercontainers]
      processors: [batch]
      exporters: [clickhouselogsexporter]

#http:
  #cors:
    #allowed_origins:
     # - <https://app.3dcerts.tech>  # URL of your Frontend application
     # - <https://admin.3dcerts.tech>
     # - <https://validation.3dcerts.tech>

<@U043243QEPK> <https://signoz-community.slack.com/archives/C04512X8STV/p1665397285651349?thread_ts=1665395934.125849&amp;cid=C04512X8STV>

<@U026KJNMVP1> we tried to integrate the signoz on our react app, but getting cors issue, we have added our frontend domain in the section defined in Enable CORS in the OTel Receiver in the document

Hi <@U026KJNMVP1> Are you available today ?

Hi issue is not with the application layer issue is with the aws config

Hi <@U044Y6A3FMK>

Make sure to also include `<http://localhost>:*` in your CORS allowed origins config:
```cors:
  allowed_origins:
    - <http://localhost>:*```

Hi <@U026KJNMVP1> Can we connect, I am facing issue in configuring MongoDB monitoring

I have followed this documentation - <https://signoz.io/docs/tutorial/mongodb-metrics/>

All the configuration was done and app is working but there is no data in signoz GUI regarding the same

<@U02SS3ZAMKQ> if you have the band width please have a look

<@U043243QEPK> The metrics can be accessed from Dashboard.
You would have to plot charts according to your need.

The Services page only shows list of services which are sending telemetry data i.e. traces in general.

Yes but i hit link several times than also no data was updated

I think the tracing is not getting connected

<!channel> I need to implement this on urgent basis, please help me out

Let's connect in the morning, I am busy with a project now

Hi <@U02SS3ZAMKQ> Please let me know when can we connect regarding the issue

I will be available at 2pm IST, if that works with you?

```curl localhost:8888/metrics | grep "^\b\w*\b" -o | uniq | sort```

<https://signoz.io/blog/mongodb-monitoring/>

<https://signoz.io/docs/tutorial/mongodb-metrics/>

<https://github.com/percona/mongodb_exporter>

<https://www.mongodb.com/docs/manual/reference/connection-string/>

<@U043243QEPK> please post here so that anyone here can 

I am unable to monitor my mongodb instance

Hi <#C04512X8STV|reactjs-config> Can anyone help us to configure monitoring for our react application as currently we are getting CORS error in monitoring our live application and we also tried configuring it with SSL but still we are unable to monitor the application