feel like I'm constantly cleaning up ~30G from this directory
@kbrock I think that the UI team is aware of this, but my guess is most of this is from the
manageiq-ui-classic clones, since every time you bin/update, a new directory for the gem is created, and the UI assets (aka: npm + yarn + webpack) are put in the gem, not in the main repo
I think Martin H. was trying to look at fixing that, but I my guess is it is a hard problem to solve, and other things take priority
Follow the drama 😂
@gtanzillo we have notifier role is enabled, even in monitoring we are getting alerts, but snmp trap is not generating , because our queue command is not running because evry time we put this command in queue(command - MiqSnmp.trap_v2) but it is not running or dequeuing from queue
@djberg96 no i just asking
Yes for only snmp trap queue messages
They are generating queue messages but still remaining in queue, are not p
@GabrielSVinha
@gtanzillo
But same thing is working in other server , i have tried everything but did not get success on that server
It may be possible that the generic workerd on the server with the notifier role active if busy deliverin gother messages of that same or higher priority
Current state of the queue message is Ready
@tarunkumaragarw_twitter
Only 1 server in the region can have the notifier role active, regardless of whether it’s enabled on multiple servers
Here @gtanzillo is saying that there is a difference between a server that has the role active and one that is only assigned (like a standby, in case a server fails).
So to answer your question, the workers on the server with the role active will pick up the message
I think you can see active vs assigned on the servers diagnostic page
Ko
I had heard that most non Linux integration will be separated, eg Windows / VMWare etc
I am concerned about how that kind of a move would affect smart state analysis on those platforms.
among other things
