Which of the following is a good use case regarding defining entities for a service?

Question

Options

• AAutomatically associate entities to services using multiple entity aliases.
• BAll of the entities have the same identifying field name.
• CBeing able to split a CPU usage KPI by host name.
• DKPI total values are aggregated from multiple different category values in the source events.

• A
  72% (21)
• B
  3% (1)
• C
  17% (5)
• D
  7% (2)

Explanation

Define entities before creating services. When you configure a service, you can specify entity matching rules based on entity aliases that automatically add the entities to your service. A is the correct answer because defining entities for a service allows you to automatically associate entities to services using multiple entity aliases. Entity aliases are alternative names or identifiers for an entity, such as host name, IP address, MAC address, or DNS name. ITSI matches entity aliases to fields in your data sources and assigns entities to services accordingly. This way, you can avoid manually adding entities to each service and ensure that your services reflect the latest changes in your environment.

No community discussion yet for this question.