summaryrefslogtreecommitdiffstats
path: root/tests/test3.json
diff options
context:
space:
mode:
authorSatoshi Fujii <fujii-satoshi@jp.fujitsu.com>2021-10-15 06:55:11 +0000
committerSatoshi Fujii <fujii-satoshi@jp.fujitsu.com>2021-10-21 11:47:22 +0000
commita8d624c0502c241feadcfba71ba1442b22d9908b (patch)
tree41bb96a9be8f054c81605eed6bc8bb85d82975b4 /tests/test3.json
parent4c058689904178714211f38bc5e5e083eaffadbf (diff)
Fix microsec timestamp not properly handled
Current heartbeat service assumes lastEpochMicrosec timestamp in VES notification is represented as milli-seconds, but some devices sends micro-sec timestamp in the field. In that case, the heartbeat notification was not working due to timestamp comparison was not done properly. Signed-off-by: Satoshi Fujii <fujii-satoshi@jp.fujitsu.com> Issue-ID: DCAEGEN2-2940 Change-Id: Id7c9241de70cb3ff7ee59cf1e2c60089ff96a42b
Diffstat (limited to 'tests/test3.json')
-rw-r--r--tests/test3.json4
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/test3.json b/tests/test3.json
index 9030267..0eaf6c1 100644
--- a/tests/test3.json
+++ b/tests/test3.json
@@ -5,12 +5,12 @@
"domain": "heartbeat",
"eventId": "mvfs10",
"eventName": "Heartbeat_vFW",
- "lastEpochMicrosec": 1548313727714,
+ "lastEpochMicrosec": 1548313727714000,
"priority": "Normal",
"reportingEntityName": "ibcx0001vm002oam001",
"sequence": 1000,
"sourceName": "SOURCE_NAME3",
- "startEpochMicrosec": 1548313727714,
+ "startEpochMicrosec": 1548313727714000,
"version": "4.0.2",
"reportingEntityId": "cc305d54-75b4-431b-adb2-eb6b9e541234",
"sourceId": "VNFA_SRC3",