Closed slacAWallace closed 4 years ago
Does this work? I'd imagine you'd want to stop the messages from ever going to the event system, not ignore them once they're already created
You mean at where the log message is generated?
Yeah. If it gets passed to the event system, you'll see the message in TwinCAT.
Stopping the log handler (which listens for events from the event system) will cause messages to get backed up in the PLC buffers. Of course, they will also not be sent off to logstash/grafana here.
@n-wbrown @klauer tell me what you think of this. I still need to pytmc it, but I think it solves both the very problematic single log-message and the trickle trip cases.
@klauer @n-wbrown poke
OK now it actually does what I was intending at least for the local trip. The global trickle trip still needs a test to target the condition I am trying to address, but at least the local trip will stop really spammy loggers from DoSing a PLC. I would appreciate feedback on how intuitive the circuit breaker settings are.
Given that you accepted my suggestions it looks like I was right in the interpretation of them. In that case, I think they're reasonably clear once you know the overall intent of the circuit breaker.
Severity Code Description Project File Line Suppression State
Error 8/5/2020 3:19:40 PM 097 ms | 'Task 3' (350): | ======================================
Error 8/5/2020 3:19:38 PM 497 ms | 'Task 3' (350): | ==========TESTS FINISHED RUNNING==========
Error 8/5/2020 3:19:38 PM 817 ms | 'Task 3' (350): | Test suites: 1
Error 8/5/2020 3:19:39 PM 137 ms | 'Task 3' (350): | Tests: 3
Error 8/5/2020 3:19:39 PM 457 ms | 'Task 3' (350): | Successful tests: 3
Error 8/5/2020 3:19:39 PM 777 ms | 'Task 3' (350): | Failed tests: 0
@klauer if this looks OK i am going to pull it in now. It would help us today.
👏 Let's see how it goes!
@n-wbrown @ghalym