SPLK-3002 · Question #102
Helga has a web service that depends on the database service to provide her website. She configures the database's "Heartbeat" KPI to be a dependency in the web service. When viewing the services in…
The correct answer is B. There is a cyclic dependency between the two services. Helga needs to make sure that database. In Splunk IT Service Intelligence (ITSI), the Service Analyzer visually represents service dependencies. A solid line between services indicates a normal one way dependency where one service's health contributes to another's service health score. However, a dotted line…
Question
Helga has a web service that depends on the database service to provide her website. She configures the database's "Heartbeat" KPI to be a dependency in the web service. When viewing the services in the Service Analyzer tree view she sees a dotted line between the database service and the web service. What is the meaning of the dotted line and how can Helga fix it?
Options
- AThe "Heartbeat" KPI is not currently affecting the web service health score. Helga needs to make
- BThere is a cyclic dependency between the two services. Helga needs to make sure that database
- CThere is a cyclic dependency between the two services. Helga needs to add additional
- DThe "Heartbeat" KPI is not currently affecting the web service health score. Helga needs to make
How the community answered
(25 responses)- A8% (2)
- B68% (17)
- C4% (1)
- D20% (5)
Explanation
In Splunk IT Service Intelligence (ITSI), the Service Analyzer visually represents service dependencies. A solid line between services indicates a normal one way dependency where one service's health contributes to another's service health score. However, a dotted line signifies a cyclic dependency, meaning that two services are defined as depending on each other in a loop. This typically happens when a service is configured to depend on another service that, directly or indirectly, also depends back on the first service. In Helga's scenario, because the web service is set to depend on the database using the Heartbeat KPI, and the configuration somehow established a reverse dependency (even inadvertently), the Service Analyzer shows the relationship as cyclic with a dotted line. To resolve this, Helga needs to check the service dependency configuration for the database service and ensure it does not mistakenly include the web service (or any chain of dependencies that leads back to it). Removing or correcting that erroneous dependency breaks the cycle, which will then change the representation to a solid line and properly reflect the dependency without circular references. It's not related to KPI importance values in this context -- importance affects health score calculation but does not cause a cyclic dependency indicator.
Topics
Community Discussion
No community discussion yet for this question.