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
Currently log-courier doesn't appear to support matching in cases where logs are spread out over arbitrary depths of sub-directories. This is commonly supported via a ".../**/.." fileglob operator in other systems.
Is there any chance this could be supported? If not, is there a way to achieve this already with log-courier?
Thanks,
Corey
The text was updated successfully, but these errors were encountered:
Looking at the code I guess you're using Go's built-in Glob function so this isn't supported in the core library right now: golang/go#11862. That ticket does reference at least one other alternative library that adds support for this though...
@driskell The logs are spread out in sub-directories that mirror the mapping of services to a hierarchical URL structure. So someone can add a new service in a sub-directory another level deep and log-courier doesn't see it anymore. This is a commercial third-party product so we don't have control over where the logs are placed. Hope that makes sense.
Currently log-courier doesn't appear to support matching in cases where logs are spread out over arbitrary depths of sub-directories. This is commonly supported via a ".../**/.." fileglob operator in other systems.
Is there any chance this could be supported? If not, is there a way to achieve this already with log-courier?
Thanks,
Corey
The text was updated successfully, but these errors were encountered: