DI-IPSC-82471
Software/Hardware Log & Telemetry Report (SHL&TR)
The Software/Hardware Log & Telemetry Report provides the format, content, and delivery requirements for aggregated telemetry data automatically collected from system logs, agents, and sensors.
Approval DateFebruary 18, 2025
AMSC Number10533
Preparing ActivityTM
Project NumberIPSC-2025-003
OPR—
DTIC ApplicableNo
GIDEP ApplicableNo
Limitation—
Applicable Forms—
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Application & Interrelationship
—
Use & Relationship
The system telemetry information report contains the format, content, and delivery requirements for aggregated information generated from the automated collection of system security, health, and status data from system logs, agents, and/or sensors.
This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.
Preparation Instructions
1Format.The format of the SHL&TR shall adhere to the format described under content. Digital delivery is encouraged.
2.1Data Types:the SHL&TR shall contain the following information types of system information:
2.1.1System Performance Metrics:data and information pertaining to the physical performance characteristics of the system. Examples include CPU usage, disk usage, memory usage, power output, rotations per minute, and number of usage cycles.
2.1.2System Health Metrics:data and information pertaining to the correct functioning of the system. Examples include error rates, response times, error codes/messages, shock measurements, and non-nominal measurements.
2.1.3User Activity Metrics:data and information pertaining to user actions and behavior. Examples include login attempts, page views, times of sessions, user inputs, subsystem/module usage, user persona information, and location data.
2.1.4Network Traffic Metrics:data related to network communications. Examples include bytes sent, bytes received, network addresses, ports and services, signal strengths, dropped packets, routing, and channel frequencies.
2.1.5Security Metrics:data and information related to hostile action or system intrusion. Examples include login failures, invalid access attempts, improper privileges escalation attempts, invalid data exfiltration attempts, and alarm activations.
2.1.6Process Metrics:data and information related to the functioning of a process or team, often by data collected from an automated workflow tracking or ticketing system. Examples include work in progress (WIP), cycle times, throughput, velocity, number of deployments, and source code measurements.
2.2Data formats:The SHL&TR shall contain data according to the following formats:
2.2.1Aggregated data files.For use in periodic delivery of aggregated data in a file format. Due to the volume of data that is generated by automated telemetry, delivery in a file format should not be requested on an as-generated basis unless automated delivery to a government-accessible database is available. Deliver according to one of the file formats:
2.2.1.1JavaScript object notation (JSON)
2.2.1.2Comma separated values (CSV)
2.2.1.3Delimiter separated file
2.2.1.4Extensible Markup Language (XML)
2.2.1.7Microsoft Excel file (.xlsx)
2.2.2Application Programming Interface/Automated Data Streams.Delivery of data via an automated data pull/delivery according to one of the following formats/methods:
2.2.2.1Representational state transfer (REST)
2.2.2.4Compatible COTS Software as specified in PWS
2.2.3Data visualization or automated report.Delivery of information in an automated console, data visualization software, or web page. Report must be accessible by the government.
Schema v3.0Community-maintained · Verify against ASSIST