# SLO/SLI

**URL:** <https://community.dynatrace.com/t/slo-sli/41396>\
**Category:** Automations\
**Tags:** slo, key-requests\
**Created:** [August 28, 2023, 8:46pm UTC](https://community.dynatrace.com/t/slo-sli/41396 "2023-08-28T20:46:03Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![derija](https://avatars.discourse-cdn.com/v4/letter/d/a87d85/32.png) [@derija](https://community.dynatrace.com/u/derija)\
**Post date:** [August 28, 2023, 8:46pm UTC](https://community.dynatrace.com/t/slo-sli/41396/1 "2023-08-28T20:46:03Z")

</div>

We are using keyRequests to mark the success on a specific java method as in:

builtin:service.keyRequest.successes.server.rate:filter(and(or(in(“dt.entity.service\_method”,entitySelector(“type(service\_method),entityName.equals(~“getSomeData~”)”))))):splitBy()

This works great but we run our VM’s as Immutable Cattle, So when a NEW deployment occurs the KeyRequest is lost as it is tied to Outgoing Service entity ID.&nbsp; The NEW VM is now under a NEW service entity ID and will require another “Mark as Key Request” to occur before Seeing in SLO. Even adding the SplitBy bridges the timeline but not any data untill the Mark as Key Request occurs again on new entity. This requires manual toil and automation outside of the event. Would making them Metrics (with DDU impact) resolve this permanently? Are there Other ways to accomplish This?

---

_[View the full topic](https://community.dynatrace.com/t/slo-sli/41396)._
