You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The frank framework supports multiple instances, but at the moment ladybug can't differ between them in its overview. To fix this, we need two things:
All framework instances, belonging to the same cluster, need to provide their instance.name to the TestTool class.
In the console, the 'instanceName' of the selected cluster member in the top right corner is passed as a query parameter to the ladybug iframe src.
Describe the Feature
The instanceName needs to be determined and set in the org.wearefrank.ladybug.TestTool instance. Most likely this needs to be done somewhere in the neighbourhood of of LadybugReportGenerator and/or IbisDebuggerAdvice.
The selected value from the dropdown has an 'instanceName':
This instanceName needs to be appended as a value for the parameter filter-application to the ladybug url. Since it's running in an iframe, that should look something like this:
Collaboration with External Companies
No, community resolution only
Anything else?
🛑 The first point can not be done at the moment. The setApplication setter is not available yet.
The second point can be integrated in the framework already since an extra request parameter will simply be ignored.
Related Problem or Business Case
The frank framework supports multiple instances, but at the moment ladybug can't differ between them in its overview. To fix this, we need two things:
instance.nameto theTestToolclass.Describe the Feature
org.wearefrank.ladybug.TestToolinstance. Most likely this needs to be done somewhere in the neighbourhood of ofLadybugReportGeneratorand/orIbisDebuggerAdvice.This instanceName needs to be appended as a value for the parameter

filter-applicationto the ladybug url. Since it's running in an iframe, that should look something like this:Collaboration with External Companies
No, community resolution only
Anything else?
🛑 The first point can not be done at the moment. The
setApplicationsetter is not available yet.The second point can be integrated in the framework already since an extra request parameter will simply be ignored.