Geneos ["Geneos"]
["Geneos > Netprobe"]["Technical Reference"]

Dynamic Entities Health

Introduction

The Dynamic Entities Health plug-in monitors the performance of Collection Agent and Netprobe communication. It tracks the state of all metric received by a probe from the Collection Agent, and all Dynamic Entities associated with a probe.

Dataviews

The plug-in produces three dataviews. These provide you with an overview of the sampling process.

Entities

The Entities section shows the status of all Dynamic Entities created by the Netprobe.

Table legend

Name Description
component Name of a proposed entity.
state

The ACCEPTED or REJECTED state of a component.

If the Gateway cannot acquire a licence token for a component it is rejected and the state is shown as UNLICENSED.

numSamplers Total number of samplers provided by a component.
numSamplersRejected Number of samplers provided by a component that have been rejected.
numStreams Number of streams provided by a component.
numStreamsUnmonitored Number of streams provided by a component but not monitored.

Invalid Metrics

The Invalid metrics section shows all metrics that are not included in an entity or stream.

Headline legend

Name Description
numberDetected The total number of invalid metrics.

Table legend

Name Description
key Key used to identify the metric. The key is the unique combination of the metric name and the metric's dimensions.
name Name of the metric.
reason

The reason the Gateway has not included the metric. These include:

  • No Mapping — no mapping exists for this metric.
  • Bad Mapping — this metric is used by a mapping that would cause an error. For example, a mapping that may create an entity with a empty name or a name that contains illegal characters.
  • Entity Rejected — this metric is associated with a rejected entity.
  • Sampler Rejected — this metric is associated with a rejected sampler.
  • Cell clash — this metric is associated with a cell that is already in use.
  • Dimension clash — this metric cannot be mapped to the row the mapping specifies because the dimensions of the datapoint do not match the dimensions of the other datapoints mapped to that row.
  • Attribute Clash — this metric conflicts with the known entity attributes.
  • Entity Unlicensed — this metric is associated with an entity that is not licensed.

 

Entity consistency

When processing an incoming datapoint, the Netprobe attempts to ensure that the attributes of existing entities remain consistent.

In general, the rules for updating attributes based on new datapoints are as follows:

  • If the current entity attribute is blank, the new datapoint is accepted and the entity attribute is updated to match the new datapoint.

  • If the new datapoint attribute is blank, then the new datapoint is accepted and the entity attribute does not change, unless the current entity attribute matches the current attribute on the metric associated with the incoming datapoint. In this case, the new datapoint is accepted and the entity attribute is removed.

  • If the current entity attribute matches the new datapoint, then the new datapoint is accepted and the entity attribute does not change.

  • If the current entity attribute differs from the new datapoint, then the new datapoint is rejected, unless the current entity attribute matches the current attribute on the metric associated with the incoming datapoint. In this case, the new datapoint is accepted and the entity attribute is updated to match the new datapoint.

As an example, consider the following sequence of datapoints:

Timestep Mapped metric Entity attributes Attributes from new datapoint Metric status Event
1 metric_1 No entity exists ENV=DEV, LOC=LDN ACCEPTED Entity created with attributes ENV=DEV, LOC=LDN
2 metric_2 ENV=DEV, LOC=LDN ENV=PRD REJECTED Attributes conflict, metric rejected.
3 metric_3 ENV=DEV, LOC=LDN APP=MyAPP ACCEPTED Entity updated to add attribute APP=MyAPP
4 metric_1 ENV=DEV,LOC=LDN,APP=MyAPP ENV=DEV,LOC=NYC ACCEPTED Entity updated to change attribute value from LOC=LDNto LOC=NYC
           

A full list of all cases is provided below for greater detail. In this table we consider an example entity with one attribute and one metric, and each row indicates an independent case.

Current entity attribute value Current metric attribute value Attribute value from new datapoint Metric status Event
NONE NONE NONE ACCEPTED Entity attribute value unchanged.
NONE ANY Att_C ACCEPTED Entity attribute value updated from NONE to Att_C.
Att_A not Att_A NONE ACCEPTED Entity attribute value unchanged.
Att_A ANY Att_A ACCEPTED Entity attribute value unchanged.
Att_A Att_A NONE ACCEPTED Entity attribute value updated from Att_A to NONE.
Att_A Att_A Att_C ACCEPTED Entity attribute value updated from Att_A to Att_C.
Att_A Att_B Att_A ACCEPTED Entity attribute value unchanged.
Att_A NONE Att_C REJECTED Entity attribute value unchanged.
Att_A Att_B Att_B REJECTED Entity attribute value unchanged.
Att_A Att_B Att_C REJECTED Entity attribute value unchanged.
         

Streams

The Streams section shows information about dynamic streams.

When a Netprobe receives an event or log type datapoint from a Collection Agent that matches a dynamic mapping, then a dynamic stream is created, or a new message is added to an existing stream.

Note: Information about invalid stream metrics are shown in the Invalid metrics section.

Headline legend

Name Description
numberCreated Total number of streams created by Gateway.

Table legend

Name Description
stream Name of the stream.
subscribers Number of samplers, such as FKM or State Tracker, that are subscribed to the stream.
messagesReceived Number of event or log type datapoints that have been posted to the stream.
messagesUnread Number of messages that have been posted to the stream but have not been read by all subscribers.
messagesLost

Total number of messages that have been lost.

Stream messages are stored in a buffer, limited to 1000 messages for each stream, until they are consumed by another component. Since the buffer has a limited size, messages will be eventually be lost if there are no subscribers, or if a subscriber does not consume messages as fast as they are produced.