Page Comparison

• All the agents running to be stopped.

• Check if all the queues in the RabbitMq is empty and stop the Platform Engine.

• Open server-config.json file and add the following at the end of the file.

"correlations" : {

        "correlationWindow" : 48,

        "correlationFrequency" : 3 ,

        "batchSize" : 2000

  },

The co-relation file is key file to build relationship. The source value of the key “fields” should contain same value as of the destination. The location of the co-relation.json file should be same as the Server-config.json file namely INSIGHTS_HOME/.Insights/ co-relation.json

[

{

"destination": {

      "toolName": "**toolname**",

      "fields": [

        "**fieldaname**"

      ]

    },

    "source": {

      "toolName" : "**toolname**",

      "fields": [

        "**fieldname**"

      ]

    },

    "relationName" : "**relationshipname**"

  }

]

 All the fields required for the correlation needs to be indexed in Neo4j which includes all the fields mentioned in the co-relation.json file and correlation fields in label DATA - uuid, toolName, correlationTime, maxCorrelationTime, inSightsTime, inSightsTimeX. jiraKeys, jiraKeyProcessed

Syntax to index the field in as follows:

create index on TOOLNAME(fieldname)

Example:

create index on :scm(jiraKeys)

create index on :DATA(uuid)

create index on : JENKINS(scmCommitId)

• Start the engine
• The new relationship will be created in the Neo4j in few seconds.

• Once all the expected relationships are created in neo4j, start all the agents.