You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Name otelcol-contrib, display name: “OpenTelemetry Collector”
Installation will require Administrative rights:
This is required to install Windows services
Installation will be machine wide:
This means no installation per user
No support for side-by-side installs:
Different versions of the collector running as a service are an atypical user case and it is at best a convenience for the developers as such it won’t be supported by the MSI.
Event Windows log:
By default the service will log to the Event Log, a corresponding Event Source will be created during the installation with the same short name as the service.
Configuration file:
Installer will copy a default configuration file to the installation folder, if the user wants to customize the config the recommendation is to NOT modify this file as it is intended to be the standard configuration for the collector and can have breaking changes between collector versions.
The default configuration will be replaced on the installation of a new version.
It will be possible to specify a custom command-line to launch the collector during install by specifying the MSI property COLLECTOR_SVC_ARGS. Including the capability to point to a different configuration file. The user is in charge of ensuring that such a file exists on the given path and is correctly written, otherwise the collector will fail to start.
Installer won’t validate any configuration parameters:
This typically requires custom MSI code and complicates build and testing.
(Per comment
on the release repo, before, re-adding an MSI to the release artifacts it is desirable to give visibility to the MSI
behavior)
MSI Design
otelcol
, display name: “OpenTelemetry Collector”otelcol-contrib
, display name: “OpenTelemetry Collector”COLLECTOR_SVC_ARGS
. Including the capability to point to a different configuration file. The user is in charge of ensuring that such a file exists on the given path and is correctly written, otherwise the collector will fail to start.Previous MSI implementation
Links to past implementation of MSI installer:
Open questions:
The text was updated successfully, but these errors were encountered: