The Revit Matrix - A Journal thru Time

Up on the Microsoft store now. A standalone app to monitor your Revit. Streams your journal files.Lets you see events and errors. Check performance. Find and open or delete journal files. Full timeline of what’s what. More to come. v.1.0.0 online now. v1.1.0 publishing now.
Rated E for Everyone.
Enjoy.
https://apps.microsoft.com/detail/9nhq816hbdzc?hl=en-US&gl=US

brilliant works! and the UI, beautiful

this is awesome, thank you!

Nice one, explored a similar concept in a hackathon recently. The true value here is ultimately scale able/cross PC/org process mining, early intervention/active prevention in my opinion. E.g. using journal warnings, machine RAM spikes to begin to know when you’re likely about to see a session or two hit the fan, offer a JIT local save or see problems emering across teams like large warning spikes, mass deletions that aren’t synced in yet etc. Bonus points if you mix in other app journalling/centralize it outside Revit like you have for a bigger picture.

I see the first easy win here is identifying conflicting add-ins when prepping your deployments. Every time you get a new Revit update, on a clean machine:

  1. Install Revit, nothing else. Open it to confirm it works. Logs in the journal tool.
  2. Add your configuration. Open it to confirm it works. Logs in the journal tool.
  3. Add the Autodesk provided add-ins. Open it to confirm it works. Logs in the journal tool.
  4. Add the 3rd party add-ins. Open it to confirm it works. Logs in the journal tool.

Those 3 steps shouldn’t have any conflicts, and any which are can usually be ignored (API_ERROR lines). The ones at the 4th step are more likely to cause conflicts, and this should be able to quickly ID which ones are conflicting where. Output the list of conflicts and you’ve got a list of vendors to reach out to to say “you need to update component _____ to version _____ to be compatible with the latest Revit release.”

Added bonus you can grab all listed DLLs being loaded by Revit and periodically run them though an vulnerabilities DB to outline what security issues may need to be addressed. Anytime a new DLL is added you have a quick warning that someone’s done something fishy and may need review (this is already turning into a big issue for a few firms as agentic coding takes root).