The Government is looking for potential Logging and Monitoring as a Service solutions as a brand new requirement. Please fill out both tabs of the attached Excel and include any capability sheets your company wants to provide either to this request for information OR directly to the individuals listed below.

This is also posted as an RFI on NASA SEWP under 333407 FA8307_RFI_LMaaS

Please email responses to the following POCs with a title of FA8307_RFI_LMaaS Response - [Contractor Name] [CAGE]

elijah.simmons.4@us.af.mil 

geoffrey.bender.1@us.af.mil 

martha.pittman@us.af.mil 

kyle.hamby.1@us.af.mil 

justin.adams.44@us.af.mil

Additional Clarifications/Q&A: 

1) Please explain how, Line 21 “Robust API for automated creation of tenants,” relates to Logging and Monitoring as a Service?

o We interpret Logging and Monitoring as passive/reactive actions that take place after a cloud          service is deployed. Our interpretation of this requirement/question seems to be related to pre-deployment activities. In other words, “automated creation” seems to be a proactive action.

o Please expand this requirement/question more or reframe the requirement/ question from a different perspective.

The Government needs an API that allows us to create tenants within a logging and monitorig solution easily so that we can separate logs and metrics by labels and scale tenants as needed . The Government has ~150 customers and needs the ability to scale the creation of each customer's space to associate their identity from our Keycloak solution to their logging and metrics tenants without each customer being able to see the others information. This is what makes the LMaaS (Logging and Monitoring as a service) solution unique beyond just the need for Logging and Monitoring.