Add Event Filtering to Text Logger
ReggieMarr opened this issue · comments
| F´ Version | |
| v3.2 | |
| Affected Component | |
| Svc.PassiveTextLogger |
Problem Description
I've setup my ActiveLoggerImplCfg.hpp like so:
/*
* ActiveLoggerImplCfg.hpp
*
* Created on: Apr 16, 2015
* Author: tcanham
*/
#ifndef ACTIVELOGGER_ACTIVELOGGERIMPLCFG_HPP_
#define ACTIVELOGGER_ACTIVELOGGERIMPLCFG_HPP_
#include <Svc/ActiveLogger/ActiveLoggerImpl.hpp>
// set default filters
enum {
FILTER_WARNING_HI_DEFAULT = true, //!< WARNING HI events are filtered at input
FILTER_WARNING_LO_DEFAULT = true, //!< WARNING LO events are filtered at input
FILTER_COMMAND_DEFAULT = true, //!< COMMAND events are filtered at input
FILTER_ACTIVITY_HI_DEFAULT = true, //!< ACTIVITY HI events are filtered at input
FILTER_ACTIVITY_LO_DEFAULT = true, //!< ACTIVITY LO events are filtered at input
FILTER_DIAGNOSTIC_DEFAULT = false, //!< DIAGNOSTIC events are filtered at input
};
enum {
TELEM_ID_FILTER_SIZE = 25, //!< Size of telemetry ID filter
};
#endif /* ACTIVELOGGER_ACTIVELOGGERIMPLCFG_HPP_ */
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.:
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: Hit Ctrl-C to quit
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: Starting init
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: Failed to initialize esup connection
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: Failed initialization
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: Component failure detected. Terminating now.
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422237) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2100 registered to port 0 slot 0
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422265) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2101 registered to port 0 slot 1
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422278) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2102 registered to port 0 slot 2
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422291) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2200 registered to port 1 slot 3
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422302) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2201 registered to port 1 slot 4
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422314) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2202 registered to port 1 slot 5
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422327) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2300 registered to port 2 slot 6
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422339) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2301 registered to port 2 slot 7
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422351) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2302 registered to port 2 slot 8
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422362) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2400 registered to port 3 slot 9
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422374) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2401 registered to port 3 slot 10
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422389) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2402 registered to port 3 slot 11
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422402) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2500 registered to port 4 slot 12
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422414) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2501 registered to port 4 slot 13
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422426) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2502 registered to port 4 slot 14
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422438) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x500 registered to port 5 slot 15
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422449) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x501 registered to port 5 slot 16
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422462) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x502 registered to port 5 slot 17
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422475) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x503 registered to port 5 slot 18
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422487) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x600 registered to port 6 slot 19
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422499) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x601 registered to port 6 slot 20
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422511) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x602 registered to port 6 slot 21
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422522) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x603 registered to port 6 slot 22
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422534) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x604 registered to port 6 slot 23
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422546) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x605 registered to port 6 slot 24
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422557) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x606 registered to port 6 slot 25
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422569) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x607 registered to port 6 slot 26
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422581) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xb00 registered to port 7 slot 27
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422593) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xb02 registered to port 7 slot 28
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422604) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xb03 registered to port 7 slot 29
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422618) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x700 registered to port 8 slot 30
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422632) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x701 registered to port 8 slot 31
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422644) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x702 registered to port 8 slot 32
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422656) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x800 registered to port 9 slot 33
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422668) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x801 registered to port 9 slot 34
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422680) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x802 registered to port 9 slot 35
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422692) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x803 registered to port 9 slot 36
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422704) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x804 registered to port 9 slot 37
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422715) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x805 registered to port 9 slot 38
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422728) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x806 registered to port 9 slot 39
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422740) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2000 registered to port 10 slot 40
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422753) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2001 registered to port 10 slot 41
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422766) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2002 registered to port 10 slot 42
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422779) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xa00 registered to port 11 slot 43
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422791) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xd00 registered to port 12 slot 44
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422804) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x4700 registered to port 13 slot 45
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422816) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x4701 registered to port 13 slot 46
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422828) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x4702 registered to port 13 slot 47
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422842) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x4703 registered to port 13 slot 48
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422854) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2600 registered to port 14 slot 49
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422867) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2601 registered to port 14 slot 50
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422878) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2602 registered to port 14 slot 51
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422890) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x2603 registered to port 14 slot 52
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422902) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x260a registered to port 14 slot 53
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422915) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x260b registered to port 14 slot 54
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422926) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x260c registered to port 14 slot 55
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422938) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x260d registered to port 14 slot 56
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422951) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x4b00 registered to port 15 slot 57
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422963) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0x4b01 registered to port 15 slot 58
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422976) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf06 registered to port 16 slot 59
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422987) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf07 registered to port 16 slot 60
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,422999) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf08 registered to port 16 slot 61
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,423010) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf09 registered to port 16 slot 62
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,423023) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf0a registered to port 16 slot 63
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,423035) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf0b registered to port 16 slot 64
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,423047) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf0c registered to port 16 slot 65
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,423059) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf00 registered to port 16 slot 66
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,423070) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf01 registered to port 16 slot 67
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,423083) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf02 registered to port 16 slot 68
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,423096) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf03 registered to port 16 slot 69
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,423108) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf04 registered to port 16 slot 70
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1280) (2:1722032802,423119) DIAGNOSTIC: (cmdDisp) OpCodeRegistered : Opcode 0xf05 registered to port 16 slot 71
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (3334) (2:1722032802,423144) WARNING_HI: (prmDb) PrmFileReadError : Parameter file read failed in stage OPEN (0) with record 0 and error 1
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (3328) (2:1722032802,423175) WARNING_LO: (prmDb) PrmIdNotFound : Parameter ID 0x4700 not found
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (3328) (2:1722032802,423190) WARNING_LO: (prmDb) PrmIdNotFound : Parameter ID 0x4701 not found
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (3328) (2:1722032802,423204) WARNING_LO: (prmDb) PrmIdNotFound : Parameter ID 0x2600 not found
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (3328) (2:1722032802,423217) WARNING_LO: (prmDb) PrmIdNotFound : Parameter ID 0x2601 not found
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (3328) (2:1722032802,423232) WARNING_LO: (prmDb) PrmIdNotFound : Parameter ID 0xf00 not found
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: [WARNING] High task priority of 100 being clamped to 99
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: [ERROR] Failed to send framed data: 2
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: [ERROR] Failed to send framed data: 2
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: [ERROR] Failed to send framed data: 2
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: [ERROR] Failed to send framed data: 2
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: [ERROR] Failed to send framed data: 2
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: [ERROR] Failed to send framed data: 2
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: [WARNING] Failed to open port with status -4 and errno 111
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (512) (2:1722032802,424554) DIAGNOSTIC: (rateGroup1Comp) RateGroupStarted : Rate group started.
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (768) (2:1722032802,424612) DIAGNOSTIC: (rateGroup2Comp) RateGroupStarted : Rate group started.
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: EVENT: (1024) (2:1722032802,424649) DIAGNOSTIC: (rateGroup3Comp) RateGroupStarted : Rate group started.
Jul 26 18:26:42 rdx-PX1-C441 FlightComputer[39862]: Starting downlink UDP connection with ip 10.10.0.246 and port 50000nSetup to send udp to 10.10.0.246:50000
Jul 26 18:26:44 rdx-PX1-C441 FlightComputer[39862]: Waiting for threads...
I'm using an instances.fpp and topology.fpp that just uses the ref example as a guide so for example I have this:
instance textLogger: Svc.PassiveTextLogger base id 0x4900
instance eventLogger: Svc.ActiveLogger base id 0x0B00 \
queue size Default.queueSize \
stack size Default.stackSize \
priority 57and this:
# ----------------------------------------------------------------------
# Pattern graph specifiers
# ----------------------------------------------------------------------
command connections instance cmdDisp
event connections instance eventLogger
param connections instance prmDb
telemetry connections instance tlmSplitter
text event connections instance textLoggerWhat 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'
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!