THWACK Tuesday Tip :: How to Run Active Diagnostics and Save for Historical Reference

FEATURED EPISODE:

How to Run Active Diagnostics and Save for Historical Reference in the Orion Platform

January 21, 2020

Most everyone can agree: one of the best ways to troubleshoot problems is to look at logs, but knowing where those logs are stored and collecting that from all around your infrastructure can be tiresome. Thankfully, you don’t have to do that because you can collect the diagnostic files from your My Orion Deployment pages for any Orion

server or any node in your monitored infrastructure.

See More Videos

Find more posts tagged with

Comments

highstone351

For what release is this ? My Orion Deployment does not show up on my screen.

(Orion Platform 2018.2 HF5, IPAM 4.7.0, NCM 7.8, CloudMonitoring 2.0.1, NPM 12.3, NTA 4.2.3, UDT 3.3.1, NetPath 1.1.3)

I have not been able to upgrade due to SQL and the servers not yet upgraded. That is another bone to pick about updates vs. upgrades.

Thanks for the help.

Mark

KMSigma.SWI

Active Diagnostics was bundled into Orion Platform 2018.2 (Troubleshoot Orion Deployment issues with Active Diagnostics ). It should be available on your system.

What version of Windows and SQL are you running? I'm sure we can help get you an upgrade path. In fact, there was a THWACK Tuesday Tips (Triple-T) video about upgrade planning: How to Check the Compatibility of Your Orion Products Before Upgrading

johnp1

Does running the diags have any significant performance impact on the server?

KMSigma.SWI

Very small impact. On my deployment with 12 Orion products installed, there was a 2% uptick on CPU and I didn't see any change in memory.

donrobert5

\m/