Script for ingestion of historical Remedy Incidents and Change tickets into Truesight Intelligence as events.
- Java Sdk 1.8
- maven
- Clone this repository.
$ git clone https://github.com/vitiwari/remedy-meter-script/
- Change the directory.
$ cd remedy-meter-script
- Run maven install
$ mvn clean install
- You can find the build jar file as remedy-meter-script-0.0.1-SNAPSHOT-full.jar
- Copy jar file to the location as dist.
- Change the incidentTemplate.json/changeTemplate.json configuration (based on description below)
- Run jar file
####java -jar remedy-meter-script-0.0.1-SNAPSHOT-full.jar <incident> <change>
The configuration file contains three major sections.
- "config":{}
- "eventDefinition":{}
- "@placeholder" : {}
| config field and value | Details/comments |
|---|---|
| "config": { | |
| "remedyHostName":"clm-XXX-XXXXX.bmc.com", | Provide the remedy Host name |
| "remedyPort":"", | Provide the remedy port (Not required) |
| "remedyUserName":"XXXXXX", | Provide the remedy UserName |
| "remedyPassword":"XXXXXX", | Provide the remedy Password |
| "tsiEventEndpoint" : "https://api.truesight-staging.bmc.com/v1/events", | TSI events endpoint based on credentials |
| "tsiApiToken":"XXXXXXXXXXXXXXXXXXXXXXXXXXXXX", | TSI API Token |
| "chunkSize":5, | No of tickets read and ingested in one chunk |
| "conditionFields":[1000000564,3], | List of fields to create condition (see below for details)* |
| "startDateTime":"2017-01-01 00:00 AM GMT+1:00", | Start Date of Remedy conditionFields |
| "endDateTime":"2017-05-29 00:00 AM GMT+1:00", | end date of remedy conditionFields |
| "retryConfig":3, | Retry configuration, in case of failure |
| "waitMsBeforeRetry":5000 | Time in ms to wait before next retry |
| }, | end |
*You can enter multiple Remedy field Ids as conditions. The reader will read based on all these fields falling in the startDat & EndDate configured.
for ex if [1000000564,3] is given & 1000000564 & 3 are fieldIds for ClosedDate & SubmittedDate correspondingly. Then Reader will read all the tickets that have closed date or submitted date falling under startDate & endDate
| Payload field and value | Details/comments |
|---|---|
| "eventDefinition": { | TSi even Payload json |
| "title": "@TITLE", | '@' refers to a placeholder whose definition* will define the value |
| "fingerprintFields": ["IncidentNumber"], | if There is no @ in the value it is treated as it is |
| ............ | ........... |
"@SEVERITY": { "fieldId":1000000162, "valueMap":{ "1000": "Critical", "2000": "High", "3000": "Medium", "4000": "Low" } },
The place holder definition contains the remedy fieldId for which values will be used. In case of valueMap is present in the definition its valueMap would be used otherwise the same value will be used.