You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test case instructs the tester to create a time-based rule generating an amp agent full report every second until 120 reports are reached.
The test case instructs the tester to verify all the reports were generated. The Print Reports option from the Manage Agents did not include the expected number of reports. The first report displayed had a timestamp of 18:26:15. The last report displayed had a timestamp of 18:27:54.
It was expected for:
⦁ Minute 19:42:20 there would be 40 messages
⦁ Minute 19:43 there would be 60 messages
⦁ Minute 19:44 there would be 20 messages, with the last report generated about 19:44:19
The timestamp on the last report displayed was 19:43:59.
The Message Groups/Minute display corresponded to the expected message distribution. The Reports Received displayed listed the last report time as 15:43:59 (assuming the difference in hours displayed to be related to time zones).
The database table vw_rpt_entries has 100 rows for the time-based rule.
It would appear there is a limit (about 99-100) to the number of reports displayed on the Agents page and the Reports Received. It may be acceptable to limit the number of reports displayed on the Agents page (user guide should discuss this), but one would expect all the reports to be listed in the Received Reports panel.
The text was updated successfully, but these errors were encountered:
d-linko
added
the
CRIT-3
Defect has moderate to mild impact on usability of delivered software for mission operations.
label
Sep 18, 2023
The max number of reports stored by the manager is dependent on VEC_MAX_IDX. Reports are still being generated by the agent but only get stored up to the max. The database can store any number of reports but the manager needs to have reports cleared to store more. This is an ION feature so i think out of scope for us to fix but we need to update documentation to note this.
The test case instructs the tester to create a time-based rule generating an amp agent full report every second until 120 reports are reached.
The test case instructs the tester to verify all the reports were generated. The Print Reports option from the Manage Agents did not include the expected number of reports. The first report displayed had a timestamp of 18:26:15. The last report displayed had a timestamp of 18:27:54.
It was expected for:
⦁ Minute 19:42:20 there would be 40 messages
⦁ Minute 19:43 there would be 60 messages
⦁ Minute 19:44 there would be 20 messages, with the last report generated about 19:44:19
The timestamp on the last report displayed was 19:43:59.
The Message Groups/Minute display corresponded to the expected message distribution. The Reports Received displayed listed the last report time as 15:43:59 (assuming the difference in hours displayed to be related to time zones).
The database table vw_rpt_entries has 100 rows for the time-based rule.
It would appear there is a limit (about 99-100) to the number of reports displayed on the Agents page and the Reports Received. It may be acceptable to limit the number of reports displayed on the Agents page (user guide should discuss this), but one would expect all the reports to be listed in the Received Reports panel.
The text was updated successfully, but these errors were encountered: