SPLK-4001 · Question #9
A customer has a very dynamic infrastructure. During every deployment, all existing instances are destroyed, and new ones are created Given this deployment model, how should a detector be created…
The correct answer is B. Create the detector. Select Alert settings, then select Ephemeral Infrastructure and enter the. According to the web search results, ephemeral infrastructure is a term that describes instances that are auto-scaled up or down, or are brought up with new code versions and discarded or recycled when the next code version is deployed. Splunk Observability Cloud has a feature…
Question
A customer has a very dynamic infrastructure. During every deployment, all existing instances are destroyed, and new ones are created Given this deployment model, how should a detector be created that will not send false notifications of instances being down?
Options
- ACreate the detector. Select Alert settings, then select Auto-Clear Alerts and enter an appropriate
- BCreate the detector. Select Alert settings, then select Ephemeral Infrastructure and enter the
- CCheck the Dynamic checkbox when creating the detector.
- DCheck the Ephemeral checkbox when creating the detector.
How the community answered
(33 responses)- A9% (3)
- B82% (27)
- C3% (1)
- D6% (2)
Explanation
According to the web search results, ephemeral infrastructure is a term that describes instances that are auto-scaled up or down, or are brought up with new code versions and discarded or recycled when the next code version is deployed. Splunk Observability Cloud has a feature that allows you to create detectors for ephemeral infrastructure without sending false notifications of instances being down. To use this feature, you need to do the following steps: Create the detector as usual, by selecting the metric or dimension that you want to monitor and alert on, and choosing the alert condition and severity level. Select Alert settings, then select Ephemeral Infrastructure. This will enable a special mode for the detector that will automatically clear alerts for instances that are expected to be terminated. Enter the expected lifetime of an instance in minutes. This is the maximum amount of time that an instance is expected to live before being replaced by a new one. For example, if your instances are replaced every hour, you can enter 60 minutes as the expected lifetime. Save the detector and activate it. With this feature, the detector will only trigger alerts when an instance stops reporting a metric unexpectedly, based on its expected lifetime. If an instance stops reporting a metric within its expected lifetime, the detector will assume that it was terminated on purpose and will not trigger
Topics
Community Discussion
No community discussion yet for this question.