Closed thezackm closed 2 years ago
I noticed this yesterday, but thought it was me as it was the first time that I have used nri-winservices.
Hi @thezackm / @markdavies71
This is the expected behavior. That config file is meant to be read by the infrastructure agent (not directly by the integration)
If you want to test the integration manually you need to create another yml config file with just the config
block of your configuration and point the config_path
to that file. It would look like:
exporter_bind_address: 127.0.0.1
exporter_bind_port: 9182
include_matching_entities:
windowsService.name:
# - regex ".*"
# - regex "app.*"
- regex "^app.*"
scrape_interval: 30s
That is the part the agent passes to the integration when invoking it. If you run it on a command prompt or powershell window, note that it has to be open as Administrator.
I'll mark this as closed but let us know if you have any other questions.
Description
Manual execution of
nri-winservices.exe
fails on known-good configuration files, while normal operations from the NR infra agent work as expected.Expected Behavior
Manual execution allows for quick testing on the YAML configuration file with output to
STDOUT
for realtime analysis.Steps to Reproduce
assuming
winservices-config.yml
is a good config that works as expected to send data to New Relic under normal operationsCurrent output:
Your Environment
Windows Server 2019 New Relic Infrastructure Agent: v1.27.3 winservices.exe: v0.5.0-beta
tested config:
Additional context
This config file works perfectly well while allowing the infrastructure agent to execute it during normal operations. These failures only occur during manual execution at the command line.