I'm not able to sent message to you directly "You have reached the limit for number of private messages that you can send for now. Please try again later." Yes, we’re focused on the federal side. ... View more

Thank you for the feedback on our UXM requirements. To dive deeper into topics like architecture, scale, and enterprise deployment, could you please point me to the appropriate account team or solutions architect we should engage with? We want to ensure our discussions are with the right experts who can provide guidance on supported designs and operational considerations. ... View more

Thank you for the feedback on our UXM requirements. To dive deeper into topics like architecture, scale, and enterprise deployment, could you please point me to the appropriate account team or solutions architect we should engage with?We want to ensure our discussions are with the right experts who can provide guidance on supported designs and operational considerations. ... View more

Thank you for the question. Below is the consolidated list of User Experience Monitoring (UXM) requirements that drive our evaluation, questions, and deliverables. These requirements are derived from mission needs and are intended to support requirements-based validation, not general product familiarization. The UXM solution must be capable of: Measuring user experience “at the glass” with quantitative, actionable metrics Detecting and diagnosing UX and performance degradations in near real time Correlating IT operator changes to service improvements or degradations regardless of change source Monitoring endpoint, network, application, and cloud service performance across the AFIN Supporting time-series analysis, anomaly detection, alerting, and capacity planning Providing centralized, standardized, and interoperable UX metrics Supporting decision-making, SLA validation, and vendor accountability Monitoring either 100% of the environment or statistically significant samples Utilizing built-in vendor metrics while maintaining transparency in metric definitions Supporting ETL, data ingestion, analytics, and data lake scalability Enabling wide data sharing without additional licensing or access costs Enforcing privacy protections (no user profiling) Supporting configurable data retention (short-term detail and long-term trends) Providing collector-level APIs for near–real-time access Meeting DoD security, RMF, logging, authentication, least-privilege, and compliance requirements Supporting patching, vulnerability management, intrusion detection, and auditability These requirements are formally captured and traceable through UXM deliverables such as the RTVM, Tool Set Evaluation Report, MVP Architecture, RMF Package, and Operations & Maintenance artifacts. Accordingly, all clarification questions are intended to determine capability alignment, architectural fit, security posture, scalability, and operational suitability of proposed solutions against these defined requirements. Please let us know if additional clarification is needed on any specific requirement area. Respectfully, Abrahameen ... View more

What data schemas are supported in the Splunk Data Lake, and is the schema enforced, semi-structured, or schema-on-read? How are time-series fields normalized across different data sources? What APIs are available for data ingestion and extraction (REST, streaming, batch), and are there any API rate limits or throughput constraints? Can external tools query the data lake directly via API, and can Splunk federate queries to external object storage such as S3? How does Splunk LDP handle large-scale time-series data (e.g., 10 TB/day), including retention and tiering options, and how does it integrate with external data lakes or analytics platforms? What role-based access controls are supported for data lake access, is the Splunk Data Lake deployment FedRAMP authorized (and at what level), and how is audit logging handled for data access and schema changes? ... View more