so after lots of adventure in Go + Delve land I've managed to dig up the cause open-telemetry/opentelemetry-collector-contrib#1367 it seems that there's basically no "Collector" present in the list which is iterates to get the metrics to serve
I tried with a "replace go.opentelemetry.io/exporter/prometheusexporter => ../opentelemetry-collector/exporter/prometheusexporter" but that didnt fair too well
what happened when you did that ?
oh, wait, no -- you should replace the entire otelcol core repo, not just the exporter
in the otelcol contrib repo, each component is a go module, but the whole core repo is a single go module
so:
replace go.opentelemetry.io/collector => ../opentelemetry-collector/
@jpkrohling could we add some kind of metricsd or debuggability to see what targets are scraped by prometheus?
that's the easiest way
Does anybody know how to resolve this? I need to use
common.StringKeyValue .
could not import go.opentelemetry.io/collector/internal/data/opentelemetry-proto-gen/common/v1 (invalid use of internal package go.opentelemetry.io/collector/internal/data/opentelemetry-proto-gen/common/v1)
2 replies
@bogdandrutu Anuraag has approved this PR after you requested his review, is it good to merge now? open-telemetry/opentelemetry-collector#2000
8 replies
Does anyone have any suggestion on this? open-telemetry/opentelemetry-collector-contrib#1426
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
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
@bogdandrutu We were wondering if it would be possible to merge open-telemetry/opentelemetry-proto#227. I don't believe we're going to be making anymore changes to the PR and it seems like everyone's approved it. It's currently blocking some other PRs that we have. Thank you!
I believe it was public before
I'm leaving for the day, but I wanted to add an item to the agenda: "Request review -- open-telemetry/opentelemetry-collector-contrib#1412"
Hi @bogdandrutu will highly appreciate your guidance regarding the next step on this PR [Resource_Attributes_To_Labels]. open-telemetry/opentelemetry-collector#2060
@bogdandrutu will appreciate a final look on this PR. open-telemetry/opentelemetry-collector#2060
Hello. I'm trying to configure the OpenTelemetry Collector (v0.4.0) with TLS with the configuration below but I see the error below in the logs. From what I see in the Change Log, 0.4.0 should support TLS. What am I doing wrong?
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
Hi @bogdandrutu wondering if we can get some guidance on this issue: open-telemetry/opentelemetry-collector-contrib#1305 we could get started on the new PR for the proposed changed if all is good.
I've been thinking about this since I first designed the current authenticator, and it does have a pluggable architecture but I don't think it would work with downstream distributions
I'm yet to try it out though
if you want to give it a try and need a quick overview of how it works, let me know
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
Hi @bogdandrutu and @tigrannajaryan would you please have a look to see if we can get this merged. We are migrating to OTLP (pdata.Metrics) from OpenCensus type. It was reviewed and approved.
open-telemetry/opentelemetry-collector-contrib#1536
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
@bogdandrutu can you please follow up on the discussion on this PR? open-telemetry/opentelemetry-collector-contrib#1497