Task #200
closedDevelop platform performance analytics dashboard
100%
Description
3.3.27 Provide analytics via dashboard/messaging platform of repository operations to include log data of database request errors, proxy errors, and supporting service components of the ORE or any critical services that could impact the performance of the ORE
Files
Updated by Christina LaRussa-Martin about 2 years ago
In order to obtain user feedback on this feature, we need to identify WHO will use the dashboards. These dashboard are monitoring the ORE itself, which is one of many software applications in the operational network.
Stakeholders who MAY look at these dashboards
ISEA - when assessing Root Cause Analysis
Operational Community - overall monitoring of ALL apps on the network
I'm thinking of these as Sys Admin tools. If that is not the intent, please clarify.
Updated by Jacob Halle about 2 years ago
- File Operational Triton Platform dashboards_ORE service applicaiton Dashboard.pdf Operational Triton Platform dashboards_ORE service applicaiton Dashboard.pdf added
2 Twelve is managing the dashboards for daily operations as the Triton platform provider. 2 Twelve has provided government with screenshots of operations. The INOCS requirements can also be satisfied by the operational dashboards within the ORE as prescribed in the PWS. 2 Twelve provided samples of the multiple dashboards in the first deliverable that highlight the different layers of the stack from storage, compute, networking and the application stack that we are managing to minimize service disruption to users consuming the ORE.
Please resee charts attached that 2 Twelve provided as a part of task order 1 as the end-to-end visibility for a cloud native, Zero Trust platform and ORE application required for modern service delivery.
Updated by Christina LaRussa-Martin about 2 years ago
When ORE is fielded in the NDP core nodes, is there an expectation that 2twelve will continue to manage daily operations of this software application> This implies a follow-on operational task.
It would be helpful to understand who from the government has engaged to date since the generic "government" is nebulous in such a large organization.
Which INOCCS requirement can be satisfied with the ORE dashboard?
Has the INOCCS team (under Sarah Swift) had an opportunity to review the dashboards? If not, we can set up a session with them for feedback. All parties should understand the interactions planned between INOCCS and ORE.Updated by Jacob Halle about 2 years ago
- File Triton platform DNS logs running implementation.jpg Triton platform DNS logs running implementation.jpg added
- File Triton platform DNS Statistics.jpg Triton platform DNS Statistics.jpg added
- File Triton platform DNS dashboard.jpg Triton platform DNS dashboard.jpg added
- File Triton platform DNS log ingestion implementation.jpg Triton platform DNS log ingestion implementation.jpg added
- File Multiple ORE Platforms hosting options DNS will support in core node 1.png Multiple ORE Platforms hosting options DNS will support in core node 1.png added
- File Multiple ORE Platforms hosting options DNS will support in core node 2.png Multiple ORE Platforms hosting options DNS will support in core node 2.png added
- File Multiple ORE Platforms hosting options DNS will support in core node 3.png Multiple ORE Platforms hosting options DNS will support in core node 3.png added
Christina Larusso comments to address in biweekly meeting - Feb 2: Feature 200: Does 2Twelve understand/have a way to pull in data in the operational environment for the dashboards (like DNS Logs)?
2 Twelve's response: Yes, please see attachments of evidence and outcomes of implementation and real time operations. These are possible due to 2 Twelve's cloud native design of Triton platform which collects logs from multiple hyperscale clouds (Azure, AWS, etc.). Note that these are the specs that NDP is supposed to provide for cloud native application (ie ORE and other potential cloud native apps) as part of the core node platform for its enabling services. This is an example of a service as well as service monitoring that is captured in PWS taskers as part of the provider functions required to ensure the feature builds of the ORE specified by the government, consumption of the ORE specified by government, and accreditation of ORE application to live in multiple government environment platforms and multi-clouds.
Also attached additional screenshots of form factor for various platform solutions that the hybrid DNS specs provided in PWS shall support and are expected to be available in the colocation on the core node from the NDP team.
Updated by Jacob Halle almost 2 years ago
- Status changed from In Progress to Closed