FA8307_RFI_LMaaS_Attachment_1.xlsx

XLSX spreadsheet 17 KB Posted

Attached to
Sources Sought / RFI for Logging and Monitoring as a Service (LMaaS).
Solicitation number
FA8307_Sources_Sought_Logging_and_Monitoring_as_a_Service_(LMaaS)
Issued by

About this file

This is a Request for Information (RFI) attachment in Excel format seeking information about enterprise-scale Logging and Monitoring as a Service (LMaaS) technology solutions for Platform One (P1). The Department of the Air Force Materiel Command Lifecycle Management Center at Joint Base San Antonio requires a solution that integrates with Kubernetes, Iron Bank, and Big Bang to monitor key metrics across P1's managed platforms and Party Bus Platform as a Service, which hosts over 150 mission software applications.

The RFI requests details on alternative licensing models, pricing information, and technical capabilities across 22 specific requirements including OIDC/SAML integration, tenant-based data protection, log retention up to 3 years, metrics retention up to 6 months, and compatibility with AWS EKS, Kubernetes, and various monitoring tools like Prometheus and Fluentbit. Vendors must provide information about transition costs, training schedules, and their willingness to enter contracts with a base year plus up to four one-year options. Responses should be emailed to five specified Air Force POCs with the subject line "FA8307_RFI_LMaaS Response - [Contractor Name] [CAGE]".

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

RFI Excel version of Word sheet Platform One (P1) has a requirement for an enterprise-scale Logging and Monitoring technology stack. This tech stack will be used to monitor key metrics in P1's managed platforms for internal use as well as for Party Bus customer use. Kubernetes, Iron Bank, and Big Bang integrations must be seamless. Logs will be retained in accordance with P1 Cyber requirements and will be exported as needed. The Party Bus Platform as a Service (PaaS) has over 150 mission software applications that must be enabled with their own multi-tenant dashboard using this technology.

Alternative License Types:
1What alternate licensing models or solutions do you offer for Logging and Monitoring as a Service (LMaaS)?

(Please provide details on available options, such as enterprise, cloud-managed, or open-source/community editions. For each licensing option/solution set, please provide how it differs from the listed license.)

2 For each licensing option/solution set, please provide how it is similar from the listed license.

(Specify any feature restrictions, scalability limitations, or support differences among the licenses (e.g., data retention, search query limits, or alerting capabilities)

3 For each licensing option/solution set, please provide how it meets the above requirements.

(Identify core features or capabilities that are shared across all options, such as log aggregation, visualization tools, and monitoring capabilities, regardless of the license type.)

4 For each licensing option/solution set, clarify how it meets the above requirements for our logging and monitoring needs.

(Please highlight specific ways in which each licensing tier can address our operational, security, and compliance needs, particularly in areas like multi-environment visibility, role-based access control, and support for compliance auditing.)

Pricing Information:
1For each license, please provide estimated transition and training costs and schedule for both transitioning to and from your proposed solution.

(Include details on onboarding costs, consulting, or configuration support required for a smooth transition. Specify any training options available, such as workshops, online courses, or documentation resources, and their associated costs.)

2 For each license, please provide any price plans associated such as monthly, trial, annual.

(Indicate if discounts are offered for longer-term contracts or high-volume deployments. For cloud-managed options, provide cost breakdowns for storage, query processing, and other usage-based charges.)

Other Considerations:
1Are there any additional features or benefits associated with the different licenses that we should consider?

For example, are advanced analytics, machine learning-based anomaly detection, or pre-built integrations with other monitoring tools included at higher licensing tiers? - Clarify any value-added services, such as dedicated account support, proactive health checks, or best-practice workshops, that come with certain licenses.

2 Is your company willing to enter into contracts with a base year with up to four one-year options? If not, how many years is your company willing to agree to?

(For longer-term contracts, specify any guarantees on pricing, renewal terms, or opportunities to adjust the contract scope to accommodate potential changes in our data volume or monitoring requirements.)

Requirements Capability Sheet

Logging and Monitoring as a Service (LMaaS) Solution :[PUT NAME HERE]
Instructions:Please select Y/NPlease select Y if Yes, N if no plans, or N/A if ready on day 1Please insert # of days from award to build capability or a date if knownPlease insert comments, questions, or concerns for each requirement if needed
Requirement:Ready on Day 1Future CapabilityEstimated date of CapabilityComments
1OIDC/SAML integration
2Ability to associate OIDC/SAML groups with tenants
3Ability to separate logs/metrics by namespace and tag accordingly for use by tenants
4Ability to export logs
5Data must be protected on a tenant-by-tenant basis
6LBAC (Label-Based Access Control) for tenant access policies to segregate data accordingly
7Single pane of glass - meaning we can federate metrics and logs to a single point per unclassified Impact Level (IL)
8Works with data sources such as Gitlab, Postgres, and Kubecost
9Custom reporting with PDFs
10Compatible with Amazon Web Services (AWS) EKS
11Deployed via Helm Chart on Kubernetes
12Technology available in Iron Bank and maintained by technology (non-P1) vendor
13Must support log retention of up to 3 years
14Must support metrics retention of up to 6 months
15Compatibility with Alloy/Opentelemetry and/or Prometheus for metrics scraping and retrieval
16Compatibility with Fluentbit and/or Alloy/Opentelemetry for logs scraping
17Dashboard views for creating panels and visualizing logs/metrics
18Ability to create "Golden dashboards" to show things such as up-time, health, and http codes
19Ability to create custom metrics forwarders for applications that have /metrics endpoints
20Ability to create custom log forwarders for non-Kubernetes/stdout logs along with ability to filter said logs to various tenants
21Robust API for automated creation of tenants
22Terraform providers or other similar capabilities for integrated scaling with current procedures

File details come from the government source that posted it. Updated .