Company > Diagnostics

Administrators working in the Medallia network can use diagnostics tools available in Medallia Setup under Company > Diagnostics.

Roles with the Setup all capability have access to these diagnostics screens:

• Last Error — Shows the last exception that occurred in reporting or Setup. Use this screen when encountering generic errors and want to debug or provide the error to those working to help resolve the issue (such as those in Medallia Technical support, Solutions architecture, Engineering, etc.).

• Unpack Survey — Shows all of the values populated for fields on the record you enter.

• Decode Viewstate — Decodes the entered viewstate into a set of readable values. The viewstate is a URL parameter (v=) Medallia Experience Cloud uses for determining what to display in a report. For example, what filters to apply.

• Performance Stats — Shows performance statistics for fields and Custom modules.

  • K-Field Benchmarking — Allows you to benchmark a potential K-field's code to see how well it performs before using it in production instances.

  • AA2 Performance Statistics — Shows performance metrics for all of the Custom modules on your instance. These metrics includes:

    • Company — Company the Custom modules belong to.

    • AA2 label — Label of the Custom module.

    • AA2 name — Name of the Custom module.

    • Role — Obsoleted.

    • Avg render time — Time it takes to render the Custom modules. In seconds or milliseconds.

    • # rendered — Number of times Custom modules have been rendered.

    • Sum render time — Average render time multiplied by the number of times Custom modules have been rendered. In seconds or milliseconds.

    • % of total — Percentage that each Custom module Sum render time takes out of the total Sum render time (that is, the sum of each Custom module Sum render time).

    • Possible optimizations — Redirects to XML and AA2 XML basics to optimize the Custom module using min-sample-size="1" instead of the hide-empty-rows="true" attribute for reports that include a dynamic-sort or static-sort element.

  • K-Field Performance Statistics — Shows performance metrics for all of the K-fields on your instance. These metrics includes:

    • Total time — Total time it takes a field to be calculated. In milliseconds or microseconds.

    • Avg. time — Average time it takes a field to be calculated. It is the Total time divided by the Count. In milliseconds or microseconds.

    • Std. Dev — Standard deviation of the Total time. In milliseconds or microseconds.

    • Min — Minimum time it takes the field to be calculated. In milliseconds or microseconds.

    • Max — Maximum time it takes the field to be calculated. In milliseconds or microseconds.

    • Count — Number of times the field has been calculated.

  • R-Field Performance Statistics — Shows performance metrics for all of the R-fields on your instance. These metrics includes:

    • Total time — Total time it takes a field to be calculated. In milliseconds or microseconds.

    • Avg. time — Average time it takes a field to be calculated. It is the Total time divided by the Count. In milliseconds or microseconds.

    • Std. Dev — Standard deviation of the Total time. In milliseconds or microseconds.

    • Min — Minimum time it takes the field to be calculated. In milliseconds or microseconds.

    • Max — Maximum time it takes the field to be calculated. In milliseconds or microseconds.

    • Count — Number of times the field has been calculated.

  Note: The three Performance Statistics reports list the Custom modules, K-fields, and R-fields (respectively) that have been opened in Experience Cloud reports. They refresh every time a deployment happens and the node is restarted. Note that the table also restarts when a running a Backfill.