hashmapinc / hashmapinc/Tempus

As a System Administrator, I would like to have a Microservice for Tag Presence

Open
#606 0 comments 0 reactions 0 assignees View on GitHub
backlog
Dominant language
Java
Stars
32
Forks
11
PR merge metrics
No merged PRs in 30d

Description

As part of Data Quality Assurance for Tempus, we need a micro-service, which will ensure that devices are sending the data elements, which are deemed mandatory for the device type to which they belong.

This user story is related to Tag Data Quality Persistence : #302 , #303. but is not an extension of it.

We now need functionality to determine the following situations at the minimum:

1.Is the Device Inactive (i.e. temporarily out-of-order)?

A Time Period will be set as a system parameter, (similar to Tag Quality Data Window). If time since last observation exceeds this, the device status will be set as Inactive'

2. Has the device gone 'Stale' (i.e. stopped until further action )?

One more time period will be set as a system parameter. If time since last observation exceeds this duration, the device status will be set as 'Stale'

3. Is the device sending all 'required attributes (tags)' ?

A set of tags will be maintained against each device type along with a time period, within which at least one reading must be available against that tag. If time since last observation for a device against the tag, exceeds this time period, an alarm will be raised.

Tag Presence must be implemented as an independent microservice. Its architecture is proposed in the diagram below.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.