Debbie Hagen

What is equally weighted paths and how do I fix it?

Blog Post created by Debbie Hagen Employee on Aug 21, 2015


Have you ever seen this red line in your model and not had values flowing between those objects?  Then when you hover over it, it says "Equally weighted paths" and maybe you thought, what the heck is that, and how do I fix it?  Well, in week's post, I'm going to help you understand what it is, and how to track it down and resolve it.


Equally weighted paths happens when you are using a database reference and the inference engine find two valid paths between the two data sets. While in Apptio, there is no requirement that you have a unique Key per dataset, it is important that you don't use two different keys to get to the same data set.  When Apptio finds this situation, it isn't sure which path to use and so it flags it as equally weighted paths.  In the picture above, I appear to have an equally weighted path between Servers and Applications.


So how do you figure out where the equally weighted path is and resolve it?  I usually start by tracing the allocation line.  To do this, I right click on the allocation line and choose Show Inference Trace.

This takes me to the Inference tab where I can see what path or paths apptio is using to relate the two data sets.  Note that both the diagram and the Tracing pane demonstrate my equally weighted path issue. 



If I look at the information in the Tracing pane, I can see that there is a Key Relationship between Servers Actuals Transform and Applications Actuals transform using "Application" and "Application Name" as the Key columns. 


And in the second Equally weighted path... it says that I also have a relationship between the same two data sets using App_Consumer and Application Name as the Key columns.

If you review the inference map for the equally weighted paths, you can see that we have two keys in Servers Actuals Transform (App Consumer and Application) linked to one key in the Applications Actuals Transform Data set (Application name).  If I actually had two separate sets of keys, then I would see two red lines between the link and each data set.

Once I know what the extra keys are, I just need to choose which keys are the best match for this relationship and turn off any extraneous keys. So in this case, I'd go into the Servers Actuals Transform data set and change the App_Consumer column to a data type of Label.  Now I only have one Key relationship between my two data sets and my values can flow smoothly from Applications into Servers.

I hope this has been helpful.  Please feel free to provide feedback on they types of tips you'd like to see here. The Apptio U team always appreciates your feedback both positive and constructive.


Thanks for learning with Apptio Education Services!

Debbie Hagen