How to troubleshoot a weird interface element appearing in Confluence.

[jairo cabello]

Hello!

This question is to know what would be your steps, in case suddenly you need to troubleshoot an issue like this:


Imagine you want to understand where the "views recently" long negative number comes from. How would you achieve it?

So far, I can't seem to identify it: Is not clearly identifies as an addon. It doesn't seem an element added to the interface through ScriptRunner, and if I inspect the element it doesn't give me too much clues on where it comes from.

Any help or suggestion will be appreciated!

[jairo cabello · Accepted solution]

After a lot of troubleshooting, we realized that the issue was on a custom-build addon that we didn't think about. After removing that unnecessary addon, Confluence is back to normal!

[Mirek]

Hi @jairo cabello! I do not recognize this view to be a OOTB Confluence interface.. Could you list all of your plugins installed in the instance or put a screenshot that would include the whole screen?

[jairo cabello]

Here is an screenshot. I hope you might recognise something!

[Mirek]

I guess this it the plugin - Viewtracker for Confluence

https://marketplace.atlassian.com/apps/28637/viewtracker-analytics-for-confluence?hosting=server&tab=overview

To be sure you would need to disable it temporary to see if that UI elements would not show.

[jairo cabello]

Thank you! But not really. That plugin does indeed work (therefore you can see the number of views next to the awful negative number).

[Mirek]

Hmm.. Overall you have so many plugins but if this is not the one it is hard to guess. It might be something that is designed for analitics like Google Analitics..  Maybe you can simply disable temporary all suspected plugins and see if there is any change or enable Safe Mode and see if this is really a plugin not any customization.

[jairo cabello]

Indeed it was that google analytics plugin. It happens to be developed by one employee that is not working in the company anymore, but after starting to disable plugins 1 by 1 we found out that it was this one the one creating this string. Weird. 

Thanks!