Are there scenarios where my metrics might be disrupted?
- Last updated
- Save as PDF
Last Updated: | Applicable Viz Versions: All
Answer
Planview Viz uses an On-prem or Cloud agent to connect to your tools. This agent then sends data from your tool connections back to Viz where it is translated into Flow Metrics based on the Flow Items and Flow States assigned to the artifacts.
Sometimes, changes to your agent, tool connections, or artifacts can lead to disruptions in your metrics.
To learn more about specific scenarios where your metrics may be disrupted, see the following sections.
Moving artifacts to a new project not selected in your artifact sets
If you move artifacts to a new project that is not selected in your artifact sets, metrics will not be collected for those artifacts until the new project is added.
Historical metrics will not change — Flow Metrics will continue to include the moved artifacts for historical dates (i.e., artifacts will appear up until the date that they were moved).
Future metrics will update accordingly — for example, you may see your Flow Load® decrease as the moved artifacts will no longer be included in your artifact sets.
Moving artifacts to a new project & deleting an old project
If you delete an old project after moving your artifacts to a new project, errors will occur while the deleted project remains in the artifact sets. Once the deleted project is removed from the artifact sets, any metrics previously collected from the deleted project will be lost.
Deleting artifacts from a tool connection
If you delete artifacts from an external tool connection, metrics will no longer be collected for those artifacts.
Historical metrics will not change — Flow Metrics will continue to include the deleted artifacts for historical dates (i.e., artifacts will appear up until the date that they were deleted).
Future metrics will update accordingly — for example, you may see your Flow Load decrease as the deleted artifacts will no longer be included in your artifact sets.
Note: In Viz, deleted artifacts or artifacts that no longer meet conditions are called de-scoped — the number of de-scoped artifacts is visible in the tool connection logs.
Deleting a tool connection on an on-prem agent & recreating it on a cloud agent
If you delete a tool connection from an On-prem agent and recreate it on a cloud agent, any metrics previously collected from the deleted tool connection will be lost.
Deleting a tool connection on a cloud agent & recreating it on an on-prem agent
If you delete a tool connection from a cloud agent and recreate it on an on-prem agent, any metrics previously collected from the deleted tool connection will be lost.
Moving a tool to a new server
If you delete a tool connection from an old server and recreate it on a new one, any metrics previously collected from the deleted tool connection will be lost.
To avoid this scenario, you should change the URL of the existing tool connection rather than deleting and recreating it.
For example, this can occur when:
- Performing an ALM upgrade — typically, individual projects are moved from an old server to a new server (with the upgraded version), and the old server is retired
Updating Artifact Type
If an artifact type is updated, metrics will no longer be collected for the updated artifacts.
Historical metrics will not change — Flow Metrics will continue to include the moved artifacts for historical dates (i.e., artifacts will appear up until the date that they were moved).
Future metrics will update accordingly — for example, you may see your Flow Load decrease as the moved artifacts will no longer be included in your artifact sets.
Updating Project IDs
If updating a Project ID, errors will occur while the old Project ID remains in an artifact set. Once the project is removed and re-added with a new ID, any metrics previously collected from the deleted project will be lost.
For example, this can occur when:
- Renaming an ALM project — the project name is the project ID
- Changing a Jira project key — the project key is the project ID
Updating Artifact IDs
When migrating a tool to a new server, artifact IDs may change, in which case the new IDs will be identified separately in Viz. This may cause inconsistencies in your metrics at the point in time where each artifact’s history was disrupted. This may also result in the appearance of duplicate artifacts where the selected timeline overlaps the date of migration.
For example, this can occur when:
- Migrating from Jira on-prem to Jira cloud — all issue IDs change