03-17-2017 07:38 AM - edited 03-17-2017 07:38 AM
Is there a way to have MineMeld prioritize miner data once they get to the output stage? Since some output feeds may be too large for certain firewalls, I want to ensure that our static blacklist is always at the top of the list. Currently new additions that don't overlap space with other miner data seem to show up at the bottom of the list causing them to get cutoff from the smaller firewalls.
03-18-2017 08:57 AM - edited 03-18-2017 08:58 AM
Hi @groehl,
my suggestion is to dedicate an output node to your static blacklist, and create an EDL entry on the devices pointing to that blacklist. Basically you can just create a separate chain where your static blacklist Miner is directly connected to a feed output node. This way the contents of your static blacklist will never been pushed down by updates from the low priority dynamic Miners.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
