common.StringKeyValue .
2 replies
8 replies
It says: bind: An attempt was made to access a socket in a way forbidden by its access permissions
We did not change the code for that part for 2 months and it just got that error now
receivers:
otlp:
protocols:
grpc:
tls_settings:
key_file: /root/test-keys/test-key
cert_file: /root/test-keys/test-key.pubError: cannot load configuration: error reading settings for receiver type "otlp": 1 error(s) decoding:
* '' has invalid keys: protocols
I opened an issue here open-telemetry/opentelemetry-collector#2101
Looking over the code I didn't see where I could register new auth modules
open-telemetry/opentelemetry-collector-contrib#1536
1 reply
open question for Go experts related to go.mod(maybe a pretty basic one). Any lead is appreciated. Thanks.
I pushed an update to opentelemetry-collector core repo. Now, from the opentelemetry-collector-contrib repo, I need to use a module (exporterhelper module) from that specific commit hash. I tried the following ways- but couldn't make it work. What's the right way to do it.
Approach-1:
require (
// go.opentelemetry.io/collector v0.14.1-0.20201106183657-c6b8f28c60b5
github.com/open-telemetry/opentelemetry-collector 5f60c7232abd6e1d3af94f8860c006f062d1c1f0
)Approach-2:
require (
go.opentelemetry.io/collector v0.14.1-0.20201106183657-c6b8f28c60b5
)
replace go.opentelemetry.io/collector/exporter/exporterhelper v0.14.1-0.20201106183657-c6b8f28c60b5 => github.com/open-telemetry/opentelemetry-collector/exporter/exporterhelper 5f60c7232abd6e1d3af94f8860c006f062d1c1f0@jpkrohling Have you seen this before with OTEL Colelctor Operator?
{"level":"error","ts":1605103614.469881,"logger":"controllers.OpenTelemetryCollector","msg":"failed to reconcile daemon sets","error":"failed to reconcile the expected daemon sets: failed to apply changes: DaemonSet.apps \"main-collector\" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{\"app.kubernetes.io/component\":\"opentelemetry-collector\", \"app.kubernetes.io/instance\":\"opentelemetry-system.main\", \"app.kubernetes.io/managed-by\":\"opentelemetry-operator\", \"app.kubernetes.io/name\":\"main-collector\", \"app.kubernetes.io/part-of\":\"opentelemetry\", \"fluxcd.io/sync-gc-mark\":\"sha256.S_o66xL9t1DMr3tS8jPOC8WO8DnOZ3mX1Rm3ZtvJS9M\"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.2.0/zapr.go:132\ngithub.com/open-telemetry/opentelemetry-operator/controllers.(*OpenTelemetryCollectorReconciler).RunTasks\n\t/workspace/controllers/opentelemetrycollector_controller.go:145\ngithub.com/open-telemetry/opentelemetry-operator/controllers.(*OpenTelemetryCollectorReconciler).Reconcile\n\t/workspace/controllers/opentelemetrycollector_controller.go:134\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:244\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:218\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:197\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1\n\t/go/pkg/mod/k8s.io/apimachinery@v0.19.3/pkg/util/wait/wait.go:155\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil\n\t/go/pkg/mod/k8s.io/apimachinery@v0.19.3/pkg/util/wait/wait.go:156\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/go/pkg/mod/k8s.io/apimachinery@v0.19.3/pkg/util/wait/wait.go:133\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/go/pkg/mod/k8s.io/apimachinery@v0.19.3/pkg/util/wait/wait.go:90"}
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
annotations:
fluxcd.io/sync-checksum: 40380fdc15e6654f514b948ee93ffef45226959a
creationTimestamp: "2020-11-10T11:46:15Z"
generation: 6
labels:
app.kubernetes.io/managed-by: opentelemetry-operator
fluxcd.io/sync-gc-mark: sha256.S_o66xL9t1DMr3tS8jPOC8WO8DnOZ3mX1Rm3ZtvJS9M
name: main
namespace: opentelemetry-system
resourceVersion: "87672233"
selfLink: /apis/opentelemetry.io/v1alpha1/namespaces/opentelemetry-system/opentelemetrycollectors/main
uid: 953f0d0c-ce61-43ed-a863-7f4ca13b6780
i forgot this channel was associated with the https://github.com/open-telemetry/opentelemetry-collector repo, so i’ve neglected to post relevant info here related to collector. instead, i’ve been posting my collector comments to the https://gitter.im/open-telemetry/opentelemetry-specification gitter channel instead over the past few days. (just issue triage logistics comments)
any chance this channel can be renamed to open-telemetry/opentelemetry-collector?
3 replies