Ankit Nayan
amith
05/12/2021, 12:54 PMAnkit Nayan
Taking that into consideration, I would like something which does not block anything you have planned on the roadmapRight
amith
05/12/2021, 5:00 PMAnkit Nayan
/swagger
endpoint, you can choose a span name (operation name) that you don't want to see in SigNoz and thus exclude this from being sent from otel-collector.
You will get to learn how otel processors work and finally, if spans are excluded, they must not be visible in the UI. Hence, an overall understanding of SigNoz.Anwesh
05/21/2021, 10:49 AMWriting test cases@User I think I can start with flattener-processor or query-service. I explored a bit for the testing framework which go provides : https://golang.org/pkg/testing/ which we can use. Also for flattener-processor. do we need to add unit test cases for util methods as such : https://github.com/Signoz/signoz/blob/main/pkg/processors/flattener/main.go#L107
Ankit Nayan
Anwesh
05/27/2021, 5:35 AMAnkit Nayan
Anwesh
05/27/2021, 6:05 AMAnkit Nayan
Anwesh
05/27/2021, 6:18 AMfunc printTraces(traces_pt *pdata.Traces)Traces where from this is populated?
// Traces is the top-level struct that is propagated through the traces pipeline.
// This is the newer version of consumerdata.Traces, but uses more efficient
// in-memory representation.
type Traces struct {
orig *[]*otlptrace.ResourceSpans
}from the code
Ankit Nayan
printTraces
is commented out at https://github.com/SigNoz/signoz/blob/main/pkg/processors/flattener/main.go#L308
process
method is automatically invoked with the data. This method is fed as parameter to goka library Input function which reads streaming data from Kafka. Have a look at https://github.com/SigNoz/signoz/blob/main/pkg/processors/flattener/main.go#L346Anwesh
05/27/2021, 6:32 AM