0% found this document useful (0 votes)
58 views

Data Model

The document outlines the structure and fields for collections that will be used to persist Webex CDR data in MongoDB. The data is organized into two levels - conferences at level 0 and legs at level 1. The conference object contains metadata fields like ID, name, time zone. The legs array contains objects with per-leg fields like user name, start/end time, phone number. Default MongoDB fields like _id are omitted.

Uploaded by

shirin
Copyright
© © All Rights Reserved
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
58 views

Data Model

The document outlines the structure and fields for collections that will be used to persist Webex CDR data in MongoDB. The data is organized into two levels - conferences at level 0 and legs at level 1. The conference object contains metadata fields like ID, name, time zone. The legs array contains objects with per-leg fields like user name, start/end time, phone number. Default MongoDB fields like _id are omitted.

Uploaded by

shirin
Copyright
© © All Rights Reserved
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 346

The following outlines, the collection for persisting Webex CDRs.

Default collection fields generated by mongoDB like _id are not explicitly outlined (and are assumed to exist for each object in
Lvl 0 - conference (Object)

Name Type
id String
ccaSpPartnerName String
customerAccountName String
siteName String
confId Integer
meetingKey Long
meetingName String
meetingType String
hostUserName String
hostTimeZone String
meetingTimeZone String
meetingStart Date
meetingEnd Date
meetingDuration Integer
hostName String
loadFileName String
createdAt Date
updatedAt Date
legs Array
Lvl 1 - legs (Array Of Objects), A conference obj has 1..n relation with leg obj

Name Type

legNo Integer
userName String
legStart Date
legEnd Date
legDuration Integer
serviceIdentifier String
sessionType String
countryCode String
country String
phoneNumber String
dnis String
ani String
trackingCode1 String
trackingCode2 String
trackingCode3 String
trackingCode4 String
trackingCode5 String
trackingCode6 String
trackingCode7 String
trackingCode8 String
trackingCode9 String
trackingCode10 String
cdrId Integer
ccaSpSubscriptionId String
ccaSpOfferType String
customerAccountNumber String
umed to exist for each object inside a collection)

Cisco CDR
Constraints Field Name Mapping Type

CCA_SP_PARTNER_NAME Direct
CUSTOMER_ACCOUNT_NAME Direct
SITE_NAME Direct
index CONFID Direct
index MEETING_KEY Direct
MEETING_NAME Direct
MEETING_TYPE Direct
HOST_LOGIN_USERNAME Direct
HOST_TIMEZONE Direct
MEETING_TIMEZONE Direct
index MEETING_START_DATE Direct
index MEETING_END_DATE Direct
MEETING_DURATION Direct
HOST_NAME Direct
Derived
Native
Native

Cisco CDR
Constraints Field Name Mapping Type

Derived
USER_NAME Direct
index DIAL_STARTTIME Direct
index DIAL_ENDTIME Direct
DURATION Direct
SERVICE_IDENTIFIER Direct
SESSION_TYPE Direct
COUNTRY_CODE Direct
COUNTRY Direct
index PHONE_NUMBER Direct
TRACKING_CODE_1 Direct
index TRACKING_CODE_2 Direct
TRACKING_CODE_3 Direct
TRACKING_CODE_4 Direct
TRACKING_CODE_5 Direct
TRACKING_CODE_6 Direct
TRACKING_CODE_7 Direct
TRACKING_CODE_8 Direct
TRACKING_CODE_9 Direct
TRACKING_CODE_10 Direct
DNIS Direct
ANI Direct
CDR_ID Direct
CCA_SP_SUBSCRIPTION_ID Direct
CCA_SP_OFFER_TYPE Direct
CUSTOMER_ACCOUNT_NUMBER Direct
Cisco CDR
Remarks

This is the filename that is used to create the conference record


The timestamp when the record was created
This is the timestamp when the record was last updated
This contains the conference legs

Cisco CDR
Remarks
Id for leg based on the position in which the leg orignially appears in the CDR.
Position starts from 1
Lvl 0 - call (Object)
Audio Codes CDR
Name Type ConstraintsField Name Mapping Type
ID String Index
legId String Index Derived
localCorrId String Index Derived
globalCorrId String Index Derived
service String Derived
nodeName String Derived
cid String cid Direct
callId String callId Direct
trunk String trunk Direct
bchan String bchan Direct
conId String conid Direct
tg String tg Direct
callingParty String Index srcphonenum Direct
calledParty String Index dstphonenum Direct
duration Integer durat Direct
termSource String trmSd Direct
termReason String trmReason Direct
setupTime Date Index setupTime Direct
connectTime Date Index connectTime Direct
releaseTime Date Index releaseTime Direct
sourceHost String SrcHost Direct
destHost String DstHost Direct
loadFileName String Derived
createdAt Date Native
updatedAt Date Index Native
auditKey String Index Derived
Audio Codes CDR
Remarks

To be derived such that it is available from SNS correlation screen. To be provided when users click the details link
Can be same as comlink conferenceId. Populated by correlator.
Populated by correlator
Multiple Services like CCA, MSDR etc.populated by correlator.
To be derived from file name. Distinguishes between mumbai, bangalore or chennai nodes

This is the filename that is used to create the conference record


The timestamp when the record was created
This is the timestamp when the record was last updated
can be concat of callid+ callingParty + setupTime
click the details link
The following outlines, the collection for persisting Comlink CDRs.
Default collection fields generated by mongoDB like _id are not explicitly outlined (and are assumed to exist for each object in
Lvl 0 - conference (Object)

id Type
id String
conferenceId String
meetingStart Date
meetingEnd Date
loadFileName String
nodeName String
auditKey String
createdAt Date
updatedAt Date
matchedAudioCodesCount Integer
legs Array
Lvl 1 - legs (Array Of Objects), A conference obj has 1..n relation with leg obj

Name Type

legNo String
legStart Date
legAnswer Date
legEnd Date
legDuration Integer
callingParty String
calledParty String
callingSipId String
calledSipId String
terminationCode String
terminatedBy String
localCorrId String
persisting Comlink CDRs.
ongoDB like _id are not explicitly outlined (and are assumed to exist for each object inside a collection)

Constraints

index
index

index

index
index

ce obj has 1..n relation with leg obj

Constraints

index
index
index

index
index
Comlink CDR
Field Name Mapping Type

Conference ID Direct
Derived
Derived
Derived
Derived
Derived
Native

Comlink CDR
Field Name Mapping Type

Derived
Start DateTime Direct
Answer DateTime Direct
End DateTime Direct
Duration(secs) Direct
Calling Party Direct
Called Party Direct
Calling SIP ID Direct
Called SIP ID Direct
Termination Code Direct
Terminated By Direct
Calculated
Comlink CDR
Remarks

Calculated from min value of legStart


Calculated from max value of legStart
This is the filename that is used to create the conference record
This would be derived from the file name
Added as part of DLAP-152.It will be populated as nodeName + conferenceId
The timestamp when the record was created
This is the timestamp when the record was last updated

This contains the conference legs

Comlink CDR
Remarks
Id for leg based on the position in which the leg orignially appears in the CDR.
Position starts from 1
The following outlines, the collection for persisting Comlink CDRs.
Default collection fields generated by mongoDB like _id are not explicitly outlined (and are assumed to exist for each object in
Lvl 0 - conference (Object)
Comlink/RTDAS/Audio Code CDR
Name Type ConstraintsField Name Mapping T Remarks
id String Native
globalCorrId String Index Derived
callingParty String Index Derived Would be calling party of A record
calledParty String Index Derived Would be called party of C leg
startTime Date Index Derived Min of legs seizure time
endTime Date Index Derived Max of legs disconnect time
duration Integer Derived
legs Array This contains all correlated legs.
createdAt Date Native
updatedAt Date Index Native
Lvl 1 - legs (Array Of Objects), A conference obj has 1..n relation with leg obj
Leg level CDR
Name Type ConstraintsField Name Mapping T Remarks
legId String Index Derived Record identifier
callingParty String Index Direct
calledParty String Index Direct
seizure Date Index Direct
answer Date Direct
disconnect Date Index Direct
nodeType String Derived
nodeName String Derived
umed to exist for each object inside a collection)

party of A record
party of C leg
Name Type Constraints
_id Mapping T
id String
auditKey String Index calculated
recordType Integer Direct
globalCallIdCallManagerId Integer Direct
globalCallIdCallId Integer Direct
origLegCallIdentifier Integer Direct
dateTimeOrigination Date Direct
origSpan Integer Direct
origIpAddr String Direct
callingPartyNumber String Direct
origCauseValue Integer Direct
origCauseDescription String calculated
origVideoCapBandWidth Integer Direct
origVideoTransportAddressPort Integer Direct
destSpan Integer Direct
destIpAddr String Direct
originalCalledPartyNumber String Direct
finalCalledPartyNumber String Direct
destCauseValue Integer Direct
destCauseDescription String calculated
destMediaCapPayLoadCapability Integer Direct
destMediaCapMaxFramesPerPacket Integer Direct
destMediaCapG723BitRate Integer Direct
destVideoCapBandWidth Integer Direct
dateTimeConnect Date Direct
dateTimeDisconnect Date Direct
destDeviceName String Direct
globalCallIdClusterId String Direct
origIpv4v6Addr String Direct
destIpv4v6Addr String Direct
incomingProtocolCallRef String Direct
outgoingProtocolCallRef String Direct
duration Integer Direct
cucmName Integer Index Direct
customerName String Index Derived
loadFileName String
createdAt Date
updatedAt Date Index
Remarks
Record Identifier
dateTimeDisconnect + globalCallIdCallId
cdrRecordType
globalCallID_callManagerId
globalCallID_callId
origLegCallIdentifier
dateTimeOrigination
origSpan
origIpAddr
callingPartyNumber
origCause_value

origVideoCap_Bandwidth
origVideoTransportAddress_Port
destSpan
destIpAddr
originalCalledPartyNumber
finalCalledPartyNumber
destCause_value

destMediaCap_payloadCapability
destMediaCap_maxFramesPerPacket
destMediaCap_g723BitRate
destVideoCap_Bandwidth
dateTimeConnect
dateTimeDisconnect
destDeviceName
globalCallId_ClusterID
origIpv4v6Addr
destIpv4v6Addr
IncomingProtocolCallRef
OutgoingProtocolCallRef
duration
globalCallId_ClusterID
getting from datasouce against nodeName(cucm name)
Load file name
Comlink CDR
Name Type Constraints Field NameMapping T Remarks
id String Record Identifier
legId String Index Derived Record Identifier for legId
localCorrId String Index Derived
globalCorrId String Index Derived
service String Derived Multiple Services like WEBEX_CCA, MSDR etc
site String Site Direct
disconnect String Index DisconnectDirect
answer Date Index Answer Direct
seizure Date Index Seizure Direct
calledParty String Index Called NumDirect
callingParty String Index Calling Nu Direct
origClli String Orig Clli Direct
termClli String Term Clli Direct
duration String Duration Direct
origTrk String Orig Trk Direct
termTrk String Term Trk Direct
completionCode String CompletionDirect
holdDuration String HoldDuratiDirect
trsnmCd String Trsnm_Cd Direct
routingSl String Routing SL Direct
origRte String Orig Rte Direct
termRte String Term Rte Direct
destination String DestinationDirect
egrLocalSigIp String EgrLocalSigDirect
egrEndPointRemote String EgrEndPoi Direct
egrEndPointRmtPort Integer EgrEndPoinDirect
egrEndPointLocal String EgrEndPoinDirect
egrEndPointLocalPort Integer EgrEndPoinDirect
ingEndPointRemote String IngEndPoi Direct
ingEndPointRmtPort Integer IngEndPoinDirect
ingEndPointLocal String IngEndPoinDirect
ingEndPointLocalPort Integer IngEndPoinDirect
ingLocSigIp String IngLocSigIPDirect
egrRemoteSigIp String EgrRemoteSDirect
igrRemoteSigIp String IgrRemoteSDirect
rteSelTrunkGr String RteSelTrunDirect
egrAudPackReceive Integer EgrAudPackDirect
egrAudPackSend Integer EgrAudPac Direct
egrPackageJitter Integer EgrPackageJDirect
egrLastLatency Integer EgrLastLat Direct
egrPackLost Integer EgrPackLosDirect
igrAudPackReceive Integer IgrAudPackDirect
igrAudPackSend Integer IgrAudPackDirect
igrPackageJitter Integer IgrPackageJDirect
igrLastLatency Integer IgrLastLateDirect
igrPackLost Integer IgrPackLostDirect
discInitiator Integer DiscInitiatoDirect
callDiscRsnEgr Integer CallDiscRsnDirect
routeLabel String RouteLabelDirect
destAdminAbbr String DestAdminDirect
country String Country Direct
city String City Direct
lcrDestination String LCR DestinaDirect
ingSigType String Ingsigtype Direct
egrSigType String Egrsigtype Direct
egrCallId String EgrCallId Direct
ingCallId String IngCallid Direct
cdrFileName String NA Derived
origCustId String OrigCustId Direct
termCustId String TermCustIdDirect
incCallgNo String IncCallgNo Direct
rteSelGateway String RteSelGatewDirect
sCalledNo String SCalledNo Direct
createdAt Date Native
updatedAt Date Index Native
WEBEX_CCA, MSDR etc
Field Name Type Sample Data
call_id String 1DA95C34-A15211E9-8104B342-46322875@10.120.102.68
orig_tn String 442034785289
dest_tn String 442078970111
start_time DateTime2019-07-09 07:29:28+0000
endtime DateTime2019-07-09 14:37:27+0000
dtmf_events String o:7803:8227983834###
answered String yes
codec String G.711 u-law/PLC
release_type String Success
term_cause_desc String 200-OK
term_init String orig
pdd Integer 969
avg_pmos_tx Float 4.19999980926513
avg_pmos_rx Float 4.19999980926513
avg_avgtripdelay_tx integer 0
avg_avgtripdelay_rx integer 0
avg_burstlength_tx Float 60
avg_burstlength_rx Float 0
avg_burstlossrate_tx Float 93.4400024414062
avg_burstlossrate_rx Float 0
avg_discard_rate_tx Float 0
avg_discard_rate_rx Float 0
avg_jitter_tx Float 0.059999998658895
avg_jitter_rx Float 0
avg_packetloss_tx Float 0
avg_packetloss_rx Float 0

Note: All the fields are fetched from external database (Vertica Db)
The following outlines, the collection for persisting datasources connection information and additional information dependin
Default collection fields generated by mongoDB like _id are not explicitly outlined (and are assumed to exist for each object in
Name Type Constraints

tag String index

dataProvider String
status String

host String
hostName String
hostIp String
port String
user String
password String

nodeName String
databaseAttributes object
sftpAttributes object
apiAttributes object

alarmCodeInventoryAttributes object
databaseAttributes-To be populated in case datasource is database
Name Type `

databaseName String
driver String
databaseType String
isSSL Boolean
sftpAttributes-To be populated in case datasource are files
Name Type Constraints

cipher String
knownHostsFile String
sourceDir String
sourceArchiveDir String
destinationDir String
isRsyncEnable Boolean
isSourceDirArchivalEnable Boolean
apiAttributes-To be populated in case datasource is api
Name Type `

apiBaseURL String
userName String
userPassword String
authHeader String
authToken String
limitToFetchRecords String
scratchLastUpdatedKey String
alarmCodeInventoryAttributes-To fetch alarm Template from alarmCodeInventory
Name Type `

alarmSourceAppType String
alarmCode String
congifurationAttributes-To maintain configuration Parameters
Name Type `

mongoDocumentTtl Integer
tional information depending on datasource
ed to exist for each object inside a collection)
Remarks

Unique identifier for record


Should be same for similar for same type of datasource
e.g:audiocodes,comlink
status should be either enabled or disabled
host should be either hostIp or hostName which the application will used for
connection

name of external datasource node e.g:Mumbai-Comlink,Mumbai-AudioCodes


Object to store additional attributes for databasse
Object to store additional attributes for sftp
Object to store additional attributes for api
Object to store alarmCodeInventory attributes to fetch alarmTemplate from
alarmCodeInventory

Remarks

Remarks

To be set to true if file transfer is to be done by rsync


To be set to true if file archival is to be enabled is on source datasource

Remarks
Remarks

Remarks

TTL value in secconds for document in mongo collection


Field Name Type Constraints
alarmId String
alarmSourceIp String
alarmSourceAppType String
alarmSourceName String
alarmSourceSite String
alarmCode String
alarmCategory String
alarmSeverity String
alarmText String
alarmCause String
alarmTimeStamp String

alarmDeliveryStatus AlarmDeliveryStatus []

alarmAssociatedAlarmId String
alarmEventType String

alarmServiceType String
alarmEmailDistributionList String
alarmTargetFMS String
alarmAdditionalInfo String
alarmEmailAdditionalInfo String
alarmKeySuffix String
alarmTtl Integer
createdAt Date
updatedAt Date
expireAt Date TTL Index

alarmSourceIp Combination forms a unique key to ensure that no duplicates are added
alarmCode
alarmCategory
alarmText
alarmKeySuffix
Remarks
uuid generated by source app
ip of source app generating the alert
Few possible values: Collector, Cdr-Api
name of source app generating the alert (e.g. hostname:Collector, hostname:Cdr-Api)
name of source site
a code associated with the alarm - this is app specific
Few possible values ALARM, ALARM CLEARED, WARNING, WARNING CLEARED
Few possible values Critical, Major, Minor
Text indicating what this alarm is
Text indicating what was the cause of the alarm
UTC Timestamp when the alarm was generated in format: YYYY-MM-dd HH:mm:ss
Array of objects to maintain delivery status of each alarm delivery mechanism with time stamp,
possible delivery mechanism values as EMAIL, API, MONOLITH, REGI.
This can't be set by API.
timestamp when the delivery was attempted successfully. This can't be set by API.
The field value will be null in all alarmCategory cases except ALARM CLEARED.
Few possible values Infra-Alert, Alert
Few possible values for Infra-Alert Event type - SNS, CCA-Webex, GSIP, Apps
For Alert Event type - GSIP-ANAMOLY,GSIP-CDRMINING
Comma separated list of email address
Comma separated target FMS
Key value pair seperated by (|) Ex- key1=value1|key2=value2
Key value pair seperated by (|) Ex- key1=value1|key2=value2
values separated by -
Ttl Value In Seconds
The timestamp when the record was created
The timestamp when the record was updated
Applicable for Alert Category.(expireAt=createdAt+alarmTtl)

duplicates are added


To Be Set By Client
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

N
Y

Y
Y
Y
Y
Y
Y
Y
N
N
N
Field Name Type
alarmId String
alarmSourceIp String
alarmSourceAppType String
alarmSourceName String
alarmSourceSite String
alarmCode String
alarmCategory String
alarmSeverity String
alarmText String
alarmCause String
alarmTimeStamp String

alarmDeliveryStatus AlarmDelivery

alarmAssociatedAlarmId String
alarmEventType String

alarmServiceType String
alarmEmailDistributionList String
alarmTargetFMS String
alarmAdditionalInfo String
alarmEmailAdditionalInfo String
alarmKeySuffix String
alarmTtl Integer
createdAt Date
updatedAt Date
Remarks
uuid generated by source app
ip of source app generating the alert
Few possible values: Collector, Cdr-Api
name of source app generating the alert (e.g. hostname:Collector, hostname:Cdr-Api)
name of source site
a code associated with the alarm - this is app specific
Few possible values ALARM, ALARM CLEARED, WARNING, WARNING CLEARED
Few possible values Critical, Major, Minor
Text indicating what this alarm is
Text indicating what was the cause of the alarm
UTC Timestamp when the alarm was generated in format: YYYY-MM-dd HH:mm:ss
Array of objects to maintain delivery status of each alarm delivery mechanism with time stamp,
possible delivery mechanism values as EMAIL, API, MONOLITH, REGI.
This can't be set by API.
timestamp when the delivery was attempted successfully. This can't be set by API.
The field value will be null in all alarmCategory cases except ALARM CLEARED.
Few possible values Infra-Alert, Alert
Few possible values for Infra-Alert Event type - SNS, CCA-Webex, GSIP, Apps
For Alert Event type - GSIP-ANAMOLY,GSIP-CDRMINING
Comma separated list of email address
Comma separated target FMS
Key value pair seperated by (|) Ex- key1=value1|key2=value2
Key value pair seperated by (|) Ex- key1=value1|key2=value2
The following outlines, the collection for persisting alarmData information depending on a alarmSourceAppType and alarmCo
Default collection fields generated by mongoDB like _id are not explicitly outlined (and are assumed to exist for each object in
Name Type Constraints

tag String index


alarmSourceAppType String index
alarmCode String index

alarmCategory String
alarmSeverity String
alarmSourceSite String

alarmText String
alarmCause String
alarmEventType String

alarmServiceType String
alarmEmailDistributionList String
alarmTargetFMS String

alarmAdditionalInfo String

alarmEmailAdditionalInfo String
alarmTtl Integer
alarmKeySuffix String

comment Striing

Sample Mapping of alarmEventType and alarmServiceType

Data Lake Data Lake

Event Type Infra-Alert Infra-Alert

ServiceType SNS CCA-Webex


tion depending on a alarmSourceAppType and alarmCode
tly outlined (and are assumed to exist for each object inside a collection)
Remarks

Unique identifier for record.Should be combination of


<alarmSourceAppTyp>-<alarmCode> e.g:Collector-001
Few possible values: Collector, Cdr-Api
a code associated with the alarm - this is app specific

Few possible values ALARM, ALARM CLEARED, ALERT.This value


can be overriden by source app generating alarm or alert
Few possible values:Critical, Major, Minor
name of source site
Text indicating what this alarm is which with <remoteHostIp>
as pattern to replace remoteIp in text
Text indicating what was the cause of the alarm
Few possible values Infra-Alert, Alert
Few possible values for Infra-Alert Event type - SNS, CCA-
Webex, GSIP, Apps
For Alert Event type - GSIP-ANAMOLY,GSIP-CDRMINING
Comma separated list of email address
Comma separated target FMS
Key value pair seperated by (|) Ex- key1=value1|
key2=value2.This value can be overriden by source app
generating alarm or alert
Key value pair seperated by (|) Ex- key1=value1|
key2=value2.This value can be overriden by source app
generating alarm or alert
Ttl Value in seconds

Brief description of the collection document record.This is just


for information purpose

Data Lake Data Lake Whiteklay CDR-


Mining
Infra-
Infra-Alert Alert Alert
Alert
CDRMINI
GSIP Apps GSIP-ANALYTICS
NG
The following outlines, the collection for persisting alertScannerCollection per Alert information depending on alertScannerGr
Default collection fields generated by mongoDB like _id are not explicitly outlined (and are assumed to exist for each object in
Name Type Constraints

tag String Unique

alertScannerGroup String Indexed


collectionName String Indexed
isAlertGeneration Enabled Boolean Indexed

isSingleAlertGenerationEna
bled Boolean

alarmCode String

alarmSourceAppType String

alarmCategoryOverride String
alarmTtlOverride Integer
alertGenerationCriterias Array Of Objects

alertAdditionalInfoParamet
ersOverride Array Of Objects
recordsSortOrder String
limitToFetchRecordsFromCo
llection Integer
limitToPackAlertsPerAlert Integer

limitToScanAlertsPerJobRun Integer

alertLastUpdatedKey Object
comment Striing

QueryCriteria,ScratchLastUpdatedKeyDetails,AlertAdditionalInfoParameterDetails Object will be used to store individual param


Name Type `

parameterName String

value String

dataType String
comparisonOperator String

dateFormat String
timeZone String

isAlarmKeySuffixParameter Boolean
n per Alert information depending on alertScannerGroup,collection name and alarmCode
outlined (and are assumed to exist for each object inside a collection)
Remarks

Unique idenifier of record.A combination of tag.<Parameter Name from


alertLastUpdatedKey Parameter would form the scratch tag in scratch collection>
Group of collection on which scanning and alert-generation would be done.e.g:rtdas-
analytics.According to alertScanner different schedular cron jobs would be scheduled to
scan group of collections at a time.
Name of Collection on which alert scan and generation will be don.
Depending on value scanning and alertGeneration would be enabled
Depending on the flag value single alert would be generated per alert and if false multiple
alerts would be packed in single alert with alaramAdditional separated by || for each
record.
A code associated with the alarm - this is app specific.Few Possible values are 001,002.A
combination of alarmCode and alarmSourceAppType will fetch the template from
alarmCodeInventory
Souce App Type Value Few possible values: Scanner, Collector,Cdr-Api.A combination of
alarmCode and alarmSourceAppType will fetch the template from alarmCodeInventory
Few possible values ALARM, ALARM CLEARED, ALERT.For Scanner it will be ALERT.This
value will override the alarmCategory value from alarmCodeInventory
TTL value
List of Query Criteria Objects which will be used as criteria for alert generation
List of AlertGenerationParameterDetails Objects which will be sent as key=value pair in
alarmAdditionalInfo field of alertGenerator.This value will override the alarmAdditionalInfo
value from alarmCodeInventory
Sort order of records.Possible Values are ascending,descending

Limit to specify no of records to be fetched that can be fetched from collection


Limit to pack maximum no of Alerts in single alert

Limit to scan maximum no of Alerts per Run


ScratchLastUpdatedKeyDetails Object which will be used used as criteria from where next
scan should start e.g if scan should start based on createdTime the
collectionname.alertLastUpdatedKey.paramerName will be tag of scratch
Brief description of the collection document record.This is just for information purpose

terDetails Object will be used to store individual paramter details for alertGenerationCriterias,alertLastUpdatedKey,alertAdditionalInfoPar
Remarks

Name of paramter which can be used in alertGenerationCriterias, alertLastUpdatedKey


alarmAdditionalInfoParamterOverride
value of criteria paramter for alertGeneration.Not Applicable for
alertAdditionalInfoParametersOverride object,alertLastUpdatedKey
Name of paramter which can be used in alertGenerationCriterias,alertLastUpdatedKey
alarmAdditionalInfoParamterOverride,.Possible Values are String,Integer,Boolean,Date
Comparsion critera which used in alertGenerationCriteras for each
paramter,alertLastUpdatedKey.Possible Values are eq,lte,gte,lt,,gt
If dataType is Data the dataFormat will be used to generate or fetch data in particulat
format.Possible Values are yyyy-MM-dd'T'HH:mm:ss.SSS'Z'
If dataType is Data the timeZone will be used to specify timeZone
Applicable for alertAdditionalInfoParametersOverride object.If set to true particular
parameter would be considering for forming alarmKeySuffixValue
y,alertAdditionalInfoParametersOverride respectively
The following outlines, the collection for persisting geoLocation request,response for bulk processing
Default collection fields generated by mongoDB like _id are not explicitly outlined (and are assumed to exist for each objec
Name Type Constraints

isProcessed Boolean
geoLocationRequest Object
geoLocationSuccessRe
sponse Object
geoLocationErrorResp
onse Object
createdAt Date

updatedAt Date

expireAt Date

geoLocationRequest-To store the geoLocationAPI /post request body


Name Type `

addressType String
preferredLanguage String
accessTechnology String
cellId Integer
locationAreaCode Integer
mobileCountryCode Integer
mobileNetworkCode Integer
primaryScramblingCod
e Integer
signalStrength Integer
arbitaryStrengthUnit Integer
timingAdvance Integer

geoLocationSuccessResponse-To store the geoLocationAPI /post Success response


Name Type `

lat Double
lon Double
accuracy Integer
address String
addressDetail Object

addressDetail-To store address components


Name Type `

area String
locality String
district String
county String
city String
state String
country String
countryCode String
postalCode String
road String

geoLocationErroResponse-To store the geoLocationAPI /post Error response


Name Type `

statusCode String
errorSource String
title String
detail String
st,response for bulk processing
tly outlined (and are assumed to exist for each object inside a collection)
Remarks

All records with isProcessed value false would be taken


for processing by cron job.Will set to true only in case of
success response or error from unwired api except for
token expiry/balance over error.
Object of geoLocationRequest

Object of geoLocationSuccessResponse

Object of geoLocationErrorResponse
The timestamp when the record was created

This is the timestamp when the record was last updated


This is the timestamp when the record would be deleted
from collection

Remarks

ess response
Remarks

Object of Address Detail

Remarks
Remarks

You might also like