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
Properties values will be matched with an exact string, unless the value to match is set between /.../. The contents within the slashes will be matched as regular expressions.
And there's also code to handle that in the agent:
If I understand the regexp matching correctly both configs should find both redis services from the docker-compose.yaml.
But only the exact matching one works - the other config throws an error.
Description
According to https://docs.newrelic.com/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations/#define-discover it should be possible to use regular expressions for the discovery:
And there's also code to handle that in the agent:
infrastructure-agent/pkg/databind/internal/discovery/fields.go
Line 40 in 35aa46d
However, I couldn't get regular expressions to work with discovery.
Maybe related - I can't remember: #1753
Steps to Reproduce
The attached debug.zip provides a docker setup which can be used to reproduce the issue.
The
docker-compose.yaml
defines two redis services:There are two infra configs for redis:
If I understand the regexp matching correctly both configs should find both redis services from the docker-compose.yaml.
But only the exact matching one works - the other config throws an error.
Success - Exact:
Error - Regexp:
How to use provided docker env:
For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5):
Suggested T-Shirt size (S, M, L, XL, Unknown):
The text was updated successfully, but these errors were encountered: