281 user friendly decommutation of received reports#332
281 user friendly decommutation of received reports#332
Conversation
… with overloaded status variable.
…nts the formal release process which also triggers publication.
…efault-adm-load-process
…ols to bring in fixes for SQL concurrency causing reliability issues.
…o 281-user-friendly-decommutation-of-received-reports
BrianSipos
left a comment
BrianSipos
left a comment
There was a problem hiding this comment.
I did not dig through changes in detail, is there expected to be an update to the grafana query style to use the item table and item position index more explicitly?
not explicitly it is pulling the data from view vw_ari_rpt_set(either using the rest endpoint or straight from the database) which is ordering the items by the index |
…ommutation-of-received-reports
BrianSipos
left a comment
BrianSipos
left a comment
There was a problem hiding this comment.
One suggested search-and-replace to make a field meaning more clear from its name.
| @@ -39,7 +39,6 @@ class Config: | |||
| time_offset: Optional[datetime] = None | |||
There was a problem hiding this comment.
This applies to other cases of this term elsewhere also: If this is the computed timestamp of the individual report, it would be better to call this "agent_time" because it is the time point at which the report was created on the Agent. Separate from the "mgr_time" which is the time the message was received on the Manager.
…ommutation-of-received-reports
|
3 participants
Overhauled querying and structures used for pulling reports from the database and responding to REST calls
The rpt items are stored individual as CBOR in database and Transcoder is used to convert to string representation.
Organized reports based off report source and will send back a list of reports that are organized based off the report definition.