Tell me what you like about Perfstack and AppOptics Metrics Explorer!

Let me know (either by emailing me at: or by replying to this thread) what your favorite, can't-live-without features are from Perfstack AND AppOptics Metrics Explorer and I'll give you 250 THWACK points for each (maximum of 500 points).

Note: If you only use one of the two, reply with what you like about the one you use and you'll get 250 points

  • For PerfStack the ability to correlate multiple metrics along the same timeline is crucial when troubleshooting.  

    For AppOptics I don't know that it's a feature, per se, but the general design of being able to drill down & identify anomalies. 

  • The ability to save Perfstack entries for display on Summary pages is huge. The interactive charting with correlation display is so powerful

    The links provided in the x Details pages that allow Perfstack to be opened directly to allow a more deep dive and interactive analysis to be performed.

    No comments on the AppOptics integration, as I do not think it is particularly good (sorry)

  • Don't use AppOptics so can't say there.

    PerfStack - always demonstrate it in my sales meetings with new customers. The ease of displaying and correlate data is fantastic. Save perfstacks for later is helpful. Shows the benefit of having one platform, Orion, to monitor the whole it infrastructure.

  • There's a lot to like about PerfStack, but I think the most fundamental, and my favorite, is the ability to show specific metrics for the whole stack at a specific point in time (or a range). It's great for finding correlation or for potentially ruling out problems at that point in time.

  • The best Perfstack feature is the autocorrelation to related metrics. Saves a heap of time searching for affected elements. 

  • I don't personally use Appstack but we use Perfstack to correlate timelines on system issues.  It's a part of our high visibility process for sensitive accounts.  Throwing everything on the network on a Perfstack lets us monitor a large variety of system issues that might affect our customers and address them quickly than we could otherwise.  

  • Here you go:

    • We copy the link and post into our ticketing system for other techs to assess
    • The fact that the instance is unique to you so if someone else follows your link and modifies yours remains unchanged.
    • The ability to bring in multiple nodes and/or specific interfaces to show the total path and not just to a single node or interface
    • Having the tool readily available on the Nodes Details widget
    • And finally the depth of metrics available to enable
  • Perfstack - Ability to corelate data from multiple metrics, there are few scenarios especially when we trying to showcase metrics for a new service or while testing a service. Lastly, as well used for root cause analysis of an issue - makes it easier to explain what resource is causing an issue in our environment.

    AppOptics - We don't use this.

  • Okey so there is a balancing issue with what and what not with Perfstack. We have ISP agnostic links to multiple sites. Monitoring the load does help but it comes at a cost due to the amount of links we monitor using perfstack. Also to note that like example you have Nexus and Palo interfaces to each other for connectivity the perfstack utilization on both links do not reflect the same. We were on 2019.4.2 until recently and had issue where correlation data was not being reflected correctly especially when "real-time" is being selected. A fix was published to the latest version so we had to upgrade. But yo can still see there is discrepancies. Now from fault finding events on the network using perfstack is what sets us apart from the other departments as we can prove something did happen in a specific timestamp to the tee if something changed. Multiple variables that can be used together to get to the nitty gritty of it. 

  • For perfstack it's gotta be the unified time axis.