Hello Google Cloud Community
I'm part of the Infra Team that is working on the Installation and configuration of the "Ops Agents" for collecting and monitoring metrics.
After the installation in some VM Servers with a
Windows OS
Windows Server 2022 Datacenter 21H2
Machine type
n2-standard-4 (4 vCPUs, 16 GB Memory)
CPU platform
Intel Cascade Lake
Architecture
x86/64
This is the error that we are getting after the installation and use the configuration of the Ops Agent.
Error:
2025-05-29T14:10:08.979-0400 error internal/queue_sender.go:57 Exporting failed. Dropping data. {"resource": {}, "otelcol.component.id": "googlecloud", "otelcol.component.kind": "exporter", "otelcol.signal": "metrics", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp xx.xx.xx:443: i/o timeout\"\nrpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp xx.xx.xx:443: i/o timeout\"\nrpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp xx.xx.xx:443: i/o timeout\"\nrpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp xx.xx.xx:443: i/o timeout\"\nrpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp xx.xx.xx:443: i/o timeout\"\nrpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp xx.xx.xx:443: i/o timeout\"\nrpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp xx.xx.xx:443: i/o timeout\"\nrpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp xx.xx.xx:443: i/o timeout\"\nrpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp xx.xx.xx:443: i/o timeout\"\nrpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp xx.xx.xx:443: i/o timeout\"", "dropped_items": 1874}
go.opentelemetry.io/collector/exporter/exporterhelper/internal.NewQueueSender.func1
C:/Users/ContainerAdministrator/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.126.0/exporterhelper/internal/queue_sender.go:57
go.opentelemetry.io/collector/exporter/exporterhelper/internal/queuebatch.(*disabledBatcher[...]).Consume
C:/Users/ContainerAdministrator/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.126.0/exporterhelper/internal/queuebatch/disabled_batcher.go:22
go.opentelemetry.io/collector/exporter/exporterhelper/internal/queuebatch.(*asyncQueue[...]).Start.func1
C:/Users/ContainerAdministrator/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.126.0/exporterhelper/internal/queuebatch/async_queue.go:47
Note: I removed the IP's and replaced for xx.xx.xx for security reasons.
And :
ConfigAgent Error main.go:88: context deadline exceeded
2025-05-02T03:02:44.5225-04:00 OSConfigAgent Error main.go:88: context deadline exceeded
After some troubleshooting session, we identified that this could be a PROXY or Networking issue.
Do you have any clue about this behavior.
Thanks all in advice.
LinkedIn
Twitter
