Parth prajapati
04/25/2024, 7:59 AMListening for requests on <http://localhost>:${PORT}
);
});
My signoz is running on "http://localhost:3301/"
And i am running my application with this command "node -r ./tracing.js app.js"
Can anyone tell me that what i am doing wrong?, what change do i need to do, or any insight ?Avneesh Kumar
04/25/2024, 4:52 AMShri Mali
04/24/2024, 5:58 PMNiklas IM
04/24/2024, 3:08 PMSHANIL t s
04/24/2024, 8:53 AMEdwin Jacques
04/23/2024, 1:24 PMPavan Kumar Dinesh
04/22/2024, 4:45 PMMalik Bagwala
04/22/2024, 1:23 PMBheem
04/20/2024, 3:11 AMKhayo Vannucci Rodrigues
04/19/2024, 8:08 PMSrinivas Anant
04/18/2024, 4:27 AMAshu
Haneef Haroon
04/15/2024, 2:35 PMMars Apps Lab
04/13/2024, 6:41 PMRobson Samir
04/13/2024, 4:25 PMRiste
04/12/2024, 12:09 PM{status: "error", errorType: "unauthorized",…}
error
:
"failed to parse jwt token: unknown signing algo: RS256"
errorType
:
"unauthorized"
status
:
"error"
This is the error, however, when I copy the auth token and substitute it for the localhost it seems to work. So I don't think it's the token that's the problem.Murat Kuru
04/12/2024, 9:44 AMdocker-compose.yaml
from [this link](https://github.com/SigNoz/signoz/blob/develop/deploy/docker/clickhouse-setup/docker-compose.yaml). However, as I was reviewing the file, I noticed that it references several outdated images, some of which have critical vulnerabilities.
For instance, the image signoz/locust:1.2.3
is specified, but the latest version available is signoz/locust:2.24.1
. Could someone shed some light on why these older versions are being used and if there are plans to update them? Alternatively, would it be advisable to simply replace them with the latest versions to ensure security and compatibility?
Here's a list of the outdated images mentioned in the YAML file:
- signoz/frontend:0.38.2
- gliderlabs/logspout:v3.2.14
- signoz/alertmanager:0.23.4
- signoz/query-service:0.38.2
- signoz/signoz-otel-collector:0.88.11
- clickhouse/clickhouse-server:23.11.1-alpine
- signoz/locust:1.2.3
(mentioned above)
- bitnami/zookeeper:3.7.1
- jaegertracing/example-hotrod:1.30
Looking forward to your insights on this.hxx
04/12/2024, 7:43 AMhxx
04/12/2024, 6:09 AMVISHNUVARDHAN VANDAVASI
04/11/2024, 2:07 PMprocessors:
batch: {}
k8sattributes:
extract:
metadata:
- k8s.namespace.name
- k8s.pod.name
- k8s.pod.uid
- k8s.pod.start_time
- k8s.deployment.name
- k8s.node.name
filter:
node_from_env_var: K8S_NODE_NAME
passthrough: false
pod_association:
- sources:
- from: resource_attribute
name: k8s.pod.ip
- sources:
- from: resource_attribute
name: k8s.pod.uid
- sources:
- from: connectionAllan Oricil
04/09/2024, 8:10 PMAllan Oricil
04/09/2024, 8:04 PMAllan Oricil
04/09/2024, 8:04 PMNoel McGrath
04/08/2024, 8:14 PMyu tu
04/07/2024, 6:08 AMAllan Oricil
04/06/2024, 8:01 PMreceivers:
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:4317
http:
endpoint: 0.0.0.0:4318
hostmetrics:
collection_interval: 30s
scrapers:
cpu: {}
disk: {}
load: {}
filesystem: {}
memory: {}
network: {}
paging: {}
process:
mute_process_name_error: true
mute_process_exe_error: true
mute_process_io_error: true
processes: {}
prometheus:
config:
global:
scrape_interval: 30s
scrape_configs:
- job_name: otel-collector-binary
static_configs:
- targets: ['localhost:8888']
awscloudwatch:
region: us-east-2
logs:
poll_interval: 1m
groups:
autodiscover:
limit: 100
processors:
batch:
send_batch_size: 1000
timeout: 10s
# Ref: <https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/resourcedetectionprocessor/README.md>
resourcedetection:
detectors: [env, system] # include ec2 for AWS, gcp for GCP and azure for Azure.
# Using OTEL_RESOURCE_ATTRIBUTES envvar, env detector adds custom labels.
timeout: 2s
system:
hostname_sources: [os] # alternatively, use [dns,os] for setting FQDN as host.name and os as fallback
extensions:
health_check: {}
zpages: {}
exporters:
otlp:
endpoint: "MY_SERVICE_IP:4317"
tls:
insecure: true
logging:
# verbosity of the logging export: detailed, normal, basic
verbosity: normal
service:
telemetry:
metrics:
address: 0.0.0.0:8888
extensions: [health_check, zpages]
pipelines:
metrics:
receivers: [otlp]
processors: [batch]
exporters: [otlp]
metrics/internal:
receivers: [prometheus, hostmetrics]
processors: [resourcedetection, batch]
exporters: [otlp]
traces:
receivers: [otlp]
processors: [batch]
exporters: [otlp]
logs:
receivers: [otlp, awscloudwatch]
processors: [batch]
exporters: [otlp]
Vedant Pravin Yerpude
04/05/2024, 10:49 AMSurya
04/05/2024, 8:02 AMSungwon
04/04/2024, 3:04 PMvyshak m
04/04/2024, 2:19 PM