Stage 1 - Collect statistics from SC 3.4

To gather Graph and Cassandra related statistics from the running instance of SC 3.4.

1. A running instance of SC 3.4.

2. cassanalyze (v 0.2) command-line utility downloaded.

1. Navigate to the home /home page of SC 3.4 where you see the Syndeia Dashboard. Scroll down to the Digital thread object count by Syndeia domain types section. You’ll see a bar graph similar to the following.

   Open

   

2. If you hover over any of the bars in the bar graph, you’ll see the count for that bar mentioned inline (as shown below).

   Open

   

3. Hover over each of the bars in the bar graph, and note down the individual counts, so e.g. in the above case, the various counts (from Graph) were as shown below.

   Artifacts: 30912 Artifact Types: 426 Containers: 1770 Container Types: 139 Relations: 16422 Relation Types: 71 Repositories: 95 Repository Types: 18

4. Now, we will gather statistics from Cassandra using the cassanalyze utility which comes as a part of the SC 3.5 downloads. The guide to cassanalyze can be found here. Run Steps (1), (2) & (3) to gather the summary data from the Steps to run the utility / tool section of the guide. The output should be similar to as shown below.

   "------------- summary (begin) -------------" {:repo-summary {:repositories {:total 96, :external 95, :internal 1}, :repositories_by_uri 96}, :cont-summary {:containers {:total 1791, :external 1564, :internal 227}, :containers_by_external_id 1564, :containers_by_external_key 1564, :containers_by_repository_key 1791}, :art-summary {:artifacts {:total 31209, :external 31175, :internal 34, :latest 29349}, :artifacts_by_external_id 31174, :artifacts_by_external_key 31158, :artifacts_by_key 31209, :artifacts_by_container_key 29349, :artifacts_by_type_key 29349}, :rel-summary {:relations {:total 16422, :external 6052, :internal 10370, :latest 15670}, :relations_by_external_id 6052, :relations_by_external_key 6052, :relations_by_key 16422, :relations_by_source_key 16422, :relations_by_target_key 16422, :relations_by_container_key 15670}, :repo-types-summary {:repository_types {:total 18, :external 17, :internal 1}}, :cont-types-summary {:container_types {:total 141, :external 140, :internal 1}, :container_types_by_external_id 140, :container_types_by_external_key 140, :container_types_by_repository_key 141}, :art-types-summary {:artifact_types {:total 431, :external 426, :internal 5}, :artifact_types_by_external_id 426, :artifact_types_by_external_key 426, :artifact_types_by_repository_key 431}, :rel-types-summary {:relation_types {:total 71, :external 13, :internal 58}, :relation_types_by_external_id 14, :relation_types_by_external_key 13, :relation_types_by_repository_key 71}} "------------- summary (end) -------------"

    

5. Graph server health check - Run the following query in the Graph view on the Syndeia web dashboard.

   g.E().has( 'sLabel', 'Relation' ).has( 'container' ).group().by( 'sKey' ).by( '_isLatest' ).unfold().findAll { i -> ! i.value.contains( 'TRUE' ) }

    

   1. If the server is healthy, this query should produce “no results” (see figure below). If you see a list of relations as the response, please contact our support team by raising a request on our helpdesk for assistance before proceeding with the migration process.

   Open

   

You should have been able to gather the statistics from both Graph and Cassandra of SC 3.4.