Rahul Tiwari
06/20/2022, 6:58 AMRitu
06/20/2022, 12:30 PMDanish Ahmad Ansari
06/20/2022, 12:41 PMxshadowlegendx
06/20/2022, 3:20 PMsuccessfully sent sample data to signoz ...
, but from my elixir app, I tested few endpoints there were no metrics or traces received. how to troubleshoot this?xshadowlegendx
06/20/2022, 3:41 PMBlake Romano
06/20/2022, 4:36 PM2022-06-20T15:38:04.634Z warn zapgrpc/zapgrpc.go:191 [core] grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: si\"" {"grpc_log": true}
Ani
06/20/2022, 7:37 PMKshitij
06/21/2022, 5:37 AMmoronmon
06/21/2022, 9:24 AM2022-06-21T09:07:19.913Z info exporterhelper/queued_retry.go:215 Exporting failed. Will retry the request after interval. {"kind": "exporter", "name": "clickhousemetricswrite", "error": "context deadline exceeded", "errorVerbose": "context deadline exceeded\<http://ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/clickhousemetricsexporter.inTransaction\n\t/src/exporter/clickhousemetricsexporter/clickhouse.go:225\ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/clickhousemetricsexporter.(*clickHouse).Write\n\t/src/exporter/clickhousemetricsexporter/clickhouse.go:305\ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/clickhousemetricsexporter.(*PrwExporter).export.func1\n\t/src/exporter/clickhousemetricsexporter/exporter.go:279\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1581|ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/clickhousemetricsexporter.inTransaction\n\t/src/exporter/clickhousemetricsexporter/clickhouse.go:225\ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/clickhousemetricsexporter.(*clickHouse).Write\n\t/src/exporter/clickhousemetricsexporter/clickhouse.go:305\ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/clickhousemetricsexporter.(*PrwExporter).export.func1\n\t/src/exporter/clickhousemetricsexporter/exporter.go:279\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1581>", "interval": "53.874924ms"}
Did I miss something?Jason Harrison
06/21/2022, 5:37 PMJason Harrison
06/21/2022, 5:37 PMPriyansh
06/21/2022, 8:05 PMImportError: dlopen(/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/grpc/_cython/cygrpc.cpython-310-darwin.so, 0x0002): tried: '/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/grpc/_cython/cygrpc.cpython-310-darwin.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/lib/cygrpc.cpython-310-darwin.so' (no such file)
Getting this error for fastAPI instrumentation, did a ton of research to debug this, still as Apple M1 is not fully development ready, can’t get anything to work.
Let me know if anyone knows how to correct this.
System - macOS 12.2.1 M1
Following this blog on SigNoz website - https://signoz.io/blog/opentelemetry-fastapi/Rishabh Tripathi
06/22/2022, 11:35 AMJason Harrison
06/23/2022, 10:36 PMSlackbot
06/24/2022, 10:42 AMT K
06/24/2022, 10:49 AMsceinfo
06/24/2022, 12:16 PMsceinfo
06/24/2022, 1:59 PMDe Scholar
06/25/2022, 4:33 PMDe Scholar
06/25/2022, 4:38 PMtracer.ts
file is this one:
'use strict';
const opentelemetry = require('@opentelemetry/sdk-node');
const {
getNodeAutoInstrumentations,
} = require('@opentelemetry/auto-instrumentations-node');
const { OTLPTraceExporter } = require('@opentelemetry/exporter-otlp-grpc');
const { Resource } = require('@opentelemetry/resources');
const {
SemanticResourceAttributes,
} = require('@opentelemetry/semantic-conventions');
// configure the SDK to export telemetry data to the console
// enable all auto-instrumentations from the meta package
const exporterOptions = {
url: 'my IP address here with the port',
};
const traceExporter = new OTLPTraceExporter(exporterOptions);
const sdk = new opentelemetry.NodeSDK({
resource: new Resource({
[SemanticResourceAttributes.SERVICE_NAME]: 'myServiceNameHere',
}),
traceExporter,
instrumentations: [getNodeAutoInstrumentations()],
});
// initialize the SDK and register with the OpenTelemetry API
// this enables the API to record telemetry
sdk
.start()
.then(() => console.log('Tracing initialized'))
.catch((error) => console.log('Error initializing tracing', error));
// gracefully shut down the SDK on process exit
process.on('SIGTERM', () => {
sdk
.shutdown()
.then(() => console.log('Tracing terminated'))
.catch((error) => console.log('Error terminating tracing', error))
.finally(() => process.exit(0));
});
module.exports = sdk;
On the log, I can see Tracing initialized
which means that it's starting successfully, but I still don't see it on signoz dashboard,
Is there anything that I might be missing?Lucas Teles
06/25/2022, 7:26 PMHome / Application
aren't shown.
I thought could be a timezone issue (because I am -3h) So I set the TZ
container environment variable, but it was unsuccessful too... when I trace the logs with --trace_exporter console
I see that every span is sent in UTC (even in my local machine)...
I don't discard a timezone issue tho...
Does someone knows what could be? or a good way to investigate...Bs Barkathulla
06/27/2022, 5:46 AMBs Barkathulla
06/27/2022, 5:51 AMBs Barkathulla
06/27/2022, 6:00 AMHimanshu Tewari
06/28/2022, 12:18 PMDe Scholar
06/28/2022, 12:52 PMSlackbot
06/28/2022, 3:50 PMVara Srinivas
06/30/2022, 1:24 PMVara Srinivas
06/30/2022, 1:32 PMmanohar mirle
06/30/2022, 2:33 PM