https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
p
b
ooook. so filelog receiver is already a part of the otel collector?
ok, that looks like it might help me a ton. thanks @Pranay Narang
i actually looked at that initially but it and the diagrams i'd seen made it appear that the collector and receiver were separate components.
p
yyeahh @brandon been using the filelog receiver from my node apps for quite sometime, its bundled with the main collector (even if you use the otel-contrib collector) so works flawlessly across the board
👍 1
b
do we know if the 
volumes
block supports globstar paths for ingesting logs? same for the 
receivers
block when specifying the specific logs to ingest for filelog
basically i have a parent folder with multiple subfolders containing logs. can i just do 
/path/to/parent/**/*.log
?
p
@brandon yeah wildcards work in the receiver
In our case we export all logs to a shared volume called /logs as different file names
b
thanks. do you know how it can handle wildcard folders and files? ideally a globstar 
**/*
format to grab all the app parent and then different subfolders, where the logs will be
actually yeah, globstar seems to have worked.
✅ 1
13 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by