@Aklapper @bd808 I guess there is some confusion regarding the official tool. The version @Rammanojpotla and I are referring to is this: https://tools.wmflabs.org/wikicontrib and is based on the code at https://github.com/wikimedia/WikiContrib The contrabadapp one which you refer is not maintained anymore and should be removed from toolforge. I guess @Rammanojpotla is going to do it and then we are all golden!

@bd808 We updated the deployed tool, but realized that Semantic UI we are using as a dependency is still fetching in some fonts from Google. @Rammanojpotla is on it to fix and re-deploy. Sorry for the delay

@Quiddity @Aklapper Fixed via https://github.com/wikimedia/WikiContrib/commit/9c7cee85c37138dd757d3bc53009784647a066d7#diff-4116fc200141126c18042468e63e9de9 I'll update this issue when the tool is updated on toolforge

@Quiddity @Aklapper Thanks for pointing this out. I will fix this ASAP and ask @Rammanojpotla to update the tool on Toolforge.

@Rammanojpotla As things are much clearer now, lets take this opportunity ( ⬆ https://phabricator.wikimedia.org/T227397#5311719) to also document and link link each UI element you are proposing to specific procedure and sample queries to achieve them. This may help @Aklapper understand better what your intentions are. For example, here is a sample you can use a possible guide to translate high level actor requirements into more detailed technical requirements and approach:

@lalit97 Thanks for the proposal. I have a few suggestions:

Hi @AdityaJ Thanks for writing this proposal. I just have a few comments:

Hi @Nikhil07prakash Thanks for this very well written proposal 👏 I don't have any specific comments except that instead of jumping directly on the UI implementation in the week of "May 27 to June 2", it may be beneficial to allocate some time on refining mockups and user interaction flow as well.

Hi @Ssomansh! Thanks for writing this proposal. The timeline is quite good 👏I just have a few comments and observations:

@Ssomansh Great questions! Me and @srishakatux brainstormed a bit about this.

@Ssomansh and @Nikhil07prakash I've reviewed your code submissions for microtasks. I may have left a few comments in the code, but overall they look nice. Keep on experimenting with similar stuff 👏 If you are starting on the UI/UX tasks and need some help, let me know.

Hey @Gopavasanth and @lalit97 Thanks for completing the microtask. I have left some comments for you on your commits (@Gopavasanth: here and @lalit97: here)

Sorry to just blurt my ideas with less context, but I <3 performance and wanted to share some stuff. Usually a series of web interfaces are useful for such a task each designed for a drill-down analysis. First the service level investigation dashboard: for queries, considering we have decent instrumentation in services, structured logs and hence metrics be be derived in elasticsearch and then queried as @aaron suggests. We can have a series of nice visualizations in kibana or Grafana (preferably) to help us out there. This would give some service level visibility. We should also have some metrics related to instances attached to the logs.

to change font color you must add changes to https://en.wikipedia.org/wiki/Special:MyPage/common.css (.css not .js)

.mw-body-content {
	color: red !important;
	font-weight: bold !important;
}