Open ReggieMarr opened 3 months ago
Console logging is done via the test logging instance. In your case it is: instance textLogger: Svc.PassiveTextLogger base id 0x4900
. Your changes above would affect the event processing bound for the ground.
The text logger instance component currently does not support filtering of events. However, you could turn off logging to the console entirely by removing this line:
text event connections instance textLogger
Oh ok good to know then, thanks for the response !
@ReggieMarr you might add an "enhancement" issue to track adding filtering to the text logger. This may be a desirable feature.
@ReggieMarr you might add an "enhancement" issue to track adding filtering to the text logger. This may be a desirable feature.
Yeah I actually started implementing it on my end, now that I know not to be looking for an existing mechanism. I was gonna request the feature by making an MR at a later date.
Sure! It is best to create an issue to track the work that will eventually become a MR. That way, if it is outside the scope of fprime core and best placed in a library or support package, we can weigh in early.
In this case, I will open this issue again and make it an enhancement request!
v3.2 |Affected Component| | Svc.PassiveTextLogger
Problem Description
I've setup my
ActiveLoggerImplCfg.hpp
like so:Context / Environment/Expected Behavior
When running a flight software build using this version of fprime I find that the stdout contains logs associated with a severity level that should otherwise be filtered out, e.g.:
I'm using an instances.fpp and topology.fpp that just uses the ref example as a guide so for example I have this:
and this:
What am I missing here? It seems like the filter applied to the ActiveLogger should prevent these logs from appearing in stdout but once I dug into things it became unclear about how to enforce this.
Let me know if there's something I can config to fix this or if this is fixed on a newer version of F'