LimaCharlie's usage-based billing enables incident responders to offer pre-deployments to their customers at almost zero cost. That is, they can deploy across an organization's entire fleet and lay dormant in ‘sleeper mode’ at a cost of just US$0.02 per endpoint per month. With agents deployed ahead of an incident, responders can offer competitive SLAs.

You can learn more about this functionality here: How does sleeper deployment work with LimaCharlie?

Eliminating Sensor Performance Impact

To eliminate any impact LC sensor deployed in a sleeper mode can have on performance, users can utilize tagging functionality.

When you tag a sensor with lc:sleep, the sensor will keep its connection to the LimaCharlie Cloud, but will disable all other functionality to avoid any impact on the system.

Tag Usage

The lc:sleep tag has no impact on billing (whether the organization leverages pure usage-based billing or "all you can eat" pricing).

The tag will prevent LimaCharlie's advanced components from loading on the agent, resulting in a sensor that still connects to the cloud, but does not do anything. This means it has no impact on the system performance-wise. No events will be collected, and nothing will be sent to the cloud. Payloads cannot be deployed to endpoints that are configured with the lc:sleep tag.

Once the lc:sleep tag is removed, then LC components will get loaded and normal functioning will resume as usual.

Did this answer your question?