Any thoughts about allowing logging by channel? #148
Nashman1970
started this conversation in
Ideas
Replies: 1 comment 1 reply
|
Hi @Nashman1970. The Resources feature in BridgeLink is what you want here, and it's superior to the old custom-lib method because it uses less resources. Head into Settings in the BridgeLink Administrator and click over to the Resources tab. You'll see a default entry already sitting there, but you'll want to leave that alone and create a new one with the Add button. Give it a name and point it at a folder on the server where you keep the jar(s). Back in BridgeLink, hit Reload Resource to pick it up. Then open whichever channels you want to use it, go to the Summary tab, scroll down to the Resources section, and check the resource you created. Save, redeploy those channels, and you'll be able to access it. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
In the old Mirth, I used Odoodo's "MetaExtender" ([https://github.com/odoodo/Mirth-MetaAppender]) to split out logging by each channel.
With a fair number of channels this has really proven to be useful, and really I can't see using Bridgelink for very many active channels without separate logging for each channel.
I looked at using odoodo's solution, but right out of the gate the setup says "copy the jar to the custom-lib sub-folder of your mirth installation" - don't have that folder in my Bridgelink install.
Maybe someone else has been able to get this to work?
All reactions