Just a grabbag of tools that I’ve designed and written at/for a company to solve a problem
I consider this category one of my strongest points as a software engineer/sre engineer. These were all self-driven in that I found/identified the problem/need for a solution an designed and implemented a solution
Weblogic Stuck Thread Checker
In python. It hit another service/rest endpoint that I wrote that returns the weblogic infrastructure details; 40 or 50 weblogic servers and their ports and other metadata. From that data, it hit the weblogic api for all servers asynchronously to return information about stuck and hogging threads. Output data was processedJinja template so it could output JSON for input into other scripts/processes or in a more human readable format. Had options to display only nodes/servers with stuck threads or all. We ran this in Jenkins so that any allowed person or group could run it
Weblogic Thread Dumps
I was very proud of this one and it was very useful. I used weblogics scripting tool WLST running in docker. It “hit” the same endpoint as above to get metadata on weblogic servers/nodes, then it ran wlst commands in order to get a thread dump of ALL 40 or 50 weblogic servers (for production env, it ran on any environment) and it checked all of the thread dumps into Git/pushed to gitlab. I started on a front end also for this so that one could visualize stuck threads over time but I never got back to it because of higher priorities. If we had an issue, we could schedule this to run say every 5 minutes so that we could easily view stuck and hogging thread history over time