Snapshot Capture Mechanism
  • Hi,

    Please tell me about the snapshot capture mechanism in Lite version.

    I understand it as the below. Please check whether my understanding is correct.

    [Outlier Requests]
    - Based on threshold settings, a BT's request that is either slow, very slow, or stalled is marked as an outlier (bad) request.
    - The product takes snapshots for all of outlier requests.
    - However, these snapshots may not have the full call graph.
    - Because the product starts capturing after a BT's request is marked as bad, the snapshot may have the partial call graph.

    [Diasnostic Sessions]
    - In Lite version, the product does not start Diagnostic Sessions automatically. We need to start it manually.
    - Meanwhile, In Pro version, the Diagnostic Sessions starts automatically when % threshold of slow transactions or error'ed transactions.
    - The snapshot captured during Diagnostic Sessions have the full call graph.

    [Periodical Sampling]
    - Based on configurable sampling frequency, the product takes snapshots.
    - These snapshots have the full call graph.


    Thanks,
    t0m


  • Hello ,

    for Outlier request you will still have information about what has caused the slowness in the application .

    Diag session,

    Yes , You will need to trigger dia session manually . In pro version of product we start it automatically.

    Periodic sampling,

    Yes ,based on sampling fequency we have snapshots.

    Regards,
    Arpit Patel
  • Hello,

    Regarding the Outlier Requests, is my understanding correct?

    From the following topic, does the product take snapshots for all of Outlier Requests?
    http://liteforums.appdynamics.com/discussion/257/i-could-not-take-a-snapshot#Item_3


    Best Regards,
    t0m

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!