Versions Compared

Version Old Version 2 New Version Current
Changes made by

Akshay Sharma

Abirami

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
top1
top1

Image Removed


Tiptip

In order to setup an Agent, it's configuration, please check the information related to the Agent in the table provided below for few DevOps tools.


Panel


S.NoProperty TypeProperty NameTool NameDescription
1GenerictoolsTimeZoneAll ToolsTime zone in which the DevOps tool(i.e. Jenkins, JIRA, GIT) is running
2GenericstartFromAll ToolsDate and Time using which the data collection of the Agent will start
3GenericisDebugAllowedAll ToolsFlag to set debugging to true or false. Useful for seeing more logs
4GenericuseResponseTemplateAll ToolsFlag to turn on the usage of Response Template
5GenericrunScheduleAll ToolsScheduler frequency of Agent in mins. Recommended - 30
6GenerictimeFieldMappingAll ToolsAdd the timeStampField here to get equivalent epoch time generated
Eg: for Git
timeFieldMapping: { commitTime : "%Y-%m-%dT%H:%M:%S.%fZ"}
7GenericResponseTemplateAll ToolsDefines the field to be collected from the Rest API calls
Eg data for Git. In the below example, fields highlighted in Blue is from the API response from the DEvOps tools and text highlighted in green are the attributes that will be stored in Neo4j. Attributes/field names in Neo4j follows camelCase Naming Convention
"responseTemplate" : {
   "sha": "commitId",
   "commit" : {
                "author" : {
                          "name": "authorName",
                          "date": "commitTime"
                          }
                    }
          }
8Tool SpecificIsEnrichmentRequiredSCMBoolean value, which takes the input whether the user wants to go for Data Enrichment(which is mandatory for creating a correlation)
9Tool SpecificSourcePropertySCMProperty of the SCM tool whose value will be picked up the engine , for processing data enrichment.
10Tool SpecificKeyPatternSCMA pattern to be entered , based on which the value from Source property will be fetched and stored.
11Tool SpecificTargetPropertySCMProperty of the SCM tool, which will store the calculated value of data Enrichment.It is used for creating correlations.
12Tool SpecificuseridHP ALMValid UserID with access to read tool data
9
13Tool SpecificpasswdHP ALMPassword of the mentioned UserID
10
14Tool SpecificbaseEndPointHP ALMUrl of the HP ALM(ex http://hostname:8080)
11
15Tool SpecifictimeStampFieldHP ALMlast-modified
12
16Tool SpecifictimeStampFormatHP ALMTime stamp format of the field specified in timeStampField
13
17Tool SpecificdataFetchCountHP ALMIt is count of the event to be fetched for one REST call
14
18Tool SpecificuseResponseTemplateHP ALM true
15
19Tool SpecificuseridJiraValid UserID with access to read tool data
16
20Tool SpecificpasswdJiraPassword of the mentioned UserID
17
21Tool SpecificbaseUrlJira#Jira_URL#/rest/api/2/search
18
22Tool SpecificuseResponseTemplateJira true
19
23Tool SpecifictimeStampFieldJiralastUpdated
20
24Tool SpecifictimeStampFormatJiraTime stamp format of the field specified in timeStampField
21
25Tool SpecificuseridArtifactoryValid UserID with access to read tool data
22
26Tool SpecificpasswdArtifactoryPassword of the mentioned UserID
23
27Tool SpecificBaseUrlArtifactoryREST URL to get list of Artifactory repositories(ex. https://<HOSTNAME>:8081/artifactory/api)
24
28Tool SpecificFirstEndPointArtifactoryREST URL to get list of  repositorie details (http://<HOSTNAME>:8081/artifactory/api/storage/)
25
29Tool SpecificuseResponseTemplateArtifactory true
26
30Tool SpecifictimeStampFieldArtifactorylastUpdated
27
31Tool SpecifictimeStampFormatArtifactoryTime stamp format of the field specified in timeStampField
28
32Tool SpecificuseridJenkinsValid UserID with access to read tool data
29
33Tool SpecificpasswdJenkinsPassword of the mentioned UserID
30
34Tool SpecificuseResponseTemplateJenkins true
31
35Tool SpecificuseAllBuildsApiJenkinsIf it is set false it will take only latest 100 elements, if is set true retrive all builds
32
36Tool SpecificbaseUrlJenkins#Jenkins_URL#
33
37Tool SpecificjenkinsMastersJenkins#Jenkins_Master_URL#
34
38Tool SpecifictimeStampFieldJenkinsbuildTimestamp
35
39Tool SpecifictimeStampFormatJenkinsTime stamp format of the field specified in timeStampField
36
40Tool Specificaccess_key_idAWSIi is the access key of an IAM user which has access all services in AWS(i.e PowerUser)
37
41Tool Specificsecret_access_keyAWSIt is the Secret key of the specified access key
38
42Tool SpecifictimeStampFieldAWSlaunchTime
39
43Tool SpecifictimeStampFormatAWSTime stamp format of the field specified in timeStampField
40
44Tool Specificvpc_idAWSSpecify the VPC ID(s)
41
45Tool SpecificuseResponseTemplateAWS false
42
46Tool SpecificAdditional LibrarySVNAgent setup includes download of boto3 library
43
47Tool SpecificusernameServiceNowValid UserName with access to read tool data which should have access to folllowing table change_request, sysapproval_approver, incident, sysapproval_group
44
48Tool SpecificpasswordServiceNowPassword of the mentioned Username
45
49Tool SpecificbaseUrlServiceNow#Service-Now_URL#
46
50Tool SpecifictimeStampFieldServiceNowSpecify the unique field in SNOW data(ex. commitTime) to refer time for each event
47
51Tool SpecifictimeStampFormatServiceNowTime stamp format of the field specified in timeStampField
48
52Tool SpecificusernameSVNValid UserName with access to read tool data of all repositories
49
53Tool SpecificpasswordSVNPassword of the mentioned Username
50
54Tool SpecificbaseUrlSVNSpecify the URL of the repositories you need to monitor in list(ex. baseUrl : ["http://<HOSTNAME>:18080/svn/repo1","http://<HOSTNAME>:18080/svn/repo2"] )
51
55Tool SpecifictimeStampFieldSVNSpecify the unique field in SVN data(ex. commitTime) to refer time for each event
52
56Tool SpecifictimeStampFormatSVNTime stamp format of the field specified in timeStampField
53
57Tool SpecificResponseTemplateSVN false
54
58Tool SpecificAdditional LibrarySVNAgent setup includes download of pysvn library
55
59Tool SpecificaccessTokenGITValid UserName access token to read GIT data of all repositories
56
60Tool SpecificgetReposGIT#GitHub_URL#/user/repos
57
61Tool SpecificcommitsBaseEndPointGIT#GitHub_URL#/repos/repo_name
58
62Tool SpecifictimeStampFieldGITcommitTime
59
63Tool SpecifictimeStampFormatGITTime stamp format of the field specified in timeStampField
60
64Tool SpecificuseridSONARValid UserID with access to read tool data
61
65Tool SpecificpasswdSONARPassword of the mentioned UserID
62
66Tool SpecificuseResponseTemplateSONAR false
63
67Tool SpecifictimeMachineapiSONARyes/no - this is based on the Sonar version
64
68Tool SpecificbaseUrlSONAR#Sonar_URL#
65
69Tool SpecifictimeStampFieldSONARbuildTimestamp
66
70Tool SpecifictimeStampFormatSONARTime stamp format of the field specified in timeStampField



DATA ENRICHMENT

Data Enrichment is a separate section added in SCM tools' configs,which deals with the post processing property of the nodes. The section should have the following properties.   

  • IsEnrichmentRequired :- Enable Post Processing.
  • SourceProperty :-Choose the property on which the post processing has to be applied
  • TargetProperty :- Name of the new property to be created.
  • KeyPattern :- Regex to be applied   

Once the property is configured in the agent management  portion, it is the role of the engine to create the property, when the node is inserted in Neo4j. The property should be created based on the regex which is configured. Later the normal flow should continue ,wherein the user is able to choose the derived property in the co-relation builder screen to link the two nodes and this relationship would be picked up by the co-relation module to create the necessary relationship.

Top Section