Running on On-Premise Windows

[alextranzact]

Describe the question Is there a way to run this on Windows on-premise?

Steps to reproduce if your question is related to an action Follow the installation and running documentation on a windows on-premise or local machine. We have tried to build the msi locally, download, wget. The installation of the OTel Collector as a windows service is successful, but is unsuccessful in starting the service. Other info: We have also been successful in starting this in Docker on the same machines.

aws-otel-collector logs:

{"level":"error","timestamp":"2022-07-27T12:03:02.289-0500","caller":"awsutil@v0.54.0/conn.go:139","message":"Unable to retrieve the region from the EC2 instance","kind":"exporter","data_type":"metrics","name":"awsemf","error":"EC2MetadataRequestError: failed to get EC2 instance identity document\ncaused by: RequestError: send request failed\ncaused by: Get \"http://169.254.169.254/latest/dynamic/instance-identity/document\": dial tcp 169.254.169.254:80: connectex: A socket operation was attempted to an unreachable network.","stack":"github.com/open-telemetry/opentelemetry-collector-contrib/internal/aws/awsutil.GetAWSConfigSession\n\tgithub.com/open-telemetry/opentelemetry-collector-contrib/internal/aws/awsutil@v0.54.0/conn.go:139\ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsemfexporter.newEmfPusher\n\tgithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsemfexporter@v0.54.0/emf_exporter.go:75\ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsemfexporter.newEmfExporter\n\tgithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsemfexporter@v0.54.0/emf_exporter.go:102\ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsemfexporter.createMetricsExporter\n\tgithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsemfexporter@v0.54.0/factory.go:63\ngo.opentelemetry.io/collector/component.CreateMetricsExporterFunc.CreateMetricsExporter\n\tgo.opentelemetry.io/collector@v0.54.0/component/exporter.go:117\ngo.opentelemetry.io/collector/service/internal/pipelines.createExporter\n\tgo.opentelemetry.io/collector@v0.54.0/service/internal/pipelines/pipelines.go:346\ngo.opentelemetry.io/collector/service/internal/pipelines.buildExporter\n\tgo.opentelemetry.io/collector@v0.54.0/service/internal/pipelines/pipelines.go:332\ngo.opentelemetry.io/collector/service/internal/pipelines.Build\n\tgo.opentelemetry.io/collector@v0.54.0/service/internal/pipelines/pipelines.go:216\ngo.opentelemetry.io/collector/service.newService\n\tgo.opentelemetry.io/collector@v0.54.0/service/service.go:68\ngo.opentelemetry.io/collector/service.(*Collector).setupConfigurationComponents\n\tgo.opentelemetry.io/collector@v0.54.0/service/collector.go:184\ngo.opentelemetry.io/collector/service.(*Collector).Run\n\tgo.opentelemetry.io/collector@v0.54.0/service/collector.go:215\ngo.opentelemetry.io/collector/service.(*windowsService).start.func1\n\tgo.opentelemetry.io/collector@v0.54.0/service/collector_windows.go:108"}

What did you expect to see? When running on EC2 Windows instance, the installation and running of the OTel Collector is successful. We would expect to see similar results when installing and running on a local or on-premise (non EC2) machine.

Environment Local or on-premise Windows machines.

Additional context Add any other context about the problem here.

[erichsueh3]

Can you share the Collector config please?

[Aneurysm9]

Please also confirm whether the AWS_REGION environment variable is set. If not, please attempt to set that to the appropriate region. The error indicated here should not be fatal unless the region is otherwise unable to be determined.

[bryan-aguilar]

Also, can you share what version of windows you are trying to run the collector on?

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions[bot]]

This issue was closed because it has been marked as stale for 30 days with no activity.