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
A time-based rule was created to generate bp full reports 1/second for 180 counts.
Agent 1.6 was selected to run this TBR starting at time 42:30. It was expected:
⦁ For minute 42: 30 messages would be generated
⦁ For minute 43: 60 messages would be generated
⦁ For minute 44: 60 messages would be generated
⦁ For minute 45: 30 messages would be generated
At time 43:33, the TBR was submitted for agent 2.6 and the same message distribution was expected.
At time 44:30, the TBR was submitted for agent 3.6 and the same message distribution was expected.
The Message Groups per Minute displayed reflected the expected distributions until 44:44. No additional points were displayed for agents after that time, the messages for minute 44 were as expected:
⦁ 45 for agent 1.6,
⦁ 44 for agent 2.6
⦁ 13 for agent 3.6
The Received Reports panel also stopped at this time. It is a known problem with the Received Reports panel that not all reports will be displayed, generally stopping at about 98-99 reports.
At this point, no other commands could be submitted for the agents without receiving an index error.
An attempt to re-add agents was executed with agent 1.6 and 2.6 being added, 3.6 was no longer available.
TBRs were submitted for agents 1.6 and 2.6 to run a report 1/sec for counts of 60, 120, and 180. Each TBR was run to completion before another TBR was started. The Message Groups per Minute panel reflected the messages at the 60 and 120 counts, but the display did not complete for 180 counts. At total of 134 messages were noted on the display.
Similar behavior was noted with the Agents tab Print report option and the Monitor tab Received reports. Refer to Issue 276.
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
A time-based rule was created to generate bp full reports 1/second for 180 counts.
Agent 1.6 was selected to run this TBR starting at time 42:30. It was expected:
⦁ For minute 42: 30 messages would be generated
⦁ For minute 43: 60 messages would be generated
⦁ For minute 44: 60 messages would be generated
⦁ For minute 45: 30 messages would be generated
At time 43:33, the TBR was submitted for agent 2.6 and the same message distribution was expected.
At time 44:30, the TBR was submitted for agent 3.6 and the same message distribution was expected.
The Message Groups per Minute displayed reflected the expected distributions until 44:44. No additional points were displayed for agents after that time, the messages for minute 44 were as expected:
⦁ 45 for agent 1.6,
⦁ 44 for agent 2.6
⦁ 13 for agent 3.6
The Received Reports panel also stopped at this time. It is a known problem with the Received Reports panel that not all reports will be displayed, generally stopping at about 98-99 reports.
At this point, no other commands could be submitted for the agents without receiving an index error.
An attempt to re-add agents was executed with agent 1.6 and 2.6 being added, 3.6 was no longer available.
TBRs were submitted for agents 1.6 and 2.6 to run a report 1/sec for counts of 60, 120, and 180. Each TBR was run to completion before another TBR was started. The Message Groups per Minute panel reflected the messages at the 60 and 120 counts, but the display did not complete for 180 counts. At total of 134 messages were noted on the display.
Similar behavior was noted with the Agents tab Print report option and the Monitor tab Received reports. Refer to Issue 276.
The text was updated successfully, but these errors were encountered: