7 OCNADD Metrics

This section includes information about Dimensions and Common Attributes of metrics for Oracle Communications Network Analytics Data Director (OCNADD).

Dimension Description

Table 7-1 Dimensions

Dimension Values Notes
HttpVersion HTTP/2.0 Specifies Http protocol version.
Method GET, PUT, POST, DELETE, PATCH HTTP method
Scheme HTTP, HTTPS, UNKNOWN Specifies the Http protocol scheme.
route_path NA Path predicate that matched the current request
status NA HTTP response code
quantile Integer values It captures the latency values with ranges as 10ms, 20ms, 40ms, 80ms, 100ms, 200ms, 500ms, 1000ms and 5000ms
instance_identifier Prefix configured in helm, UNKNOWN Prefix of the pod configured in helm when there are multiple instances in same deployment
3rd_party_consumer_name or consumer_name - Name of the 3rd party consumer application as configured from the UI
destination_endpoint IP/FQDN Destination IP address or FQDN
processor_node_id - Stream processor node id in aggregation service
serviceId serviceType-N It is the identifier for the service instance used for registration with health monitoring service
serviceType CONSUMER_ADAPTER, CONFIGURATION, ALARM, AGGREGATION-NRF, AGGREGATION-SCP, OCNADD-ADMIN-SVC The ocnadd service type.
service

ocnaddnrfaggregation,ocnaddseppaggregation, ocnaddscpaggregation,ocnaddadminservice,ocnaddconfiguration, ocnaddhealthmonitoring,<app_name>-adapter

 The name of the data director microservice service
request_type HTTP2, H2C, TCP, TCP_SECURED Type of the data feed created using UI, this will be used to identify if the feed is for HTTP2 or Synthetic packet
destination_endpoint URI It is the REST URI for the 3rd party monitoring application configured on the data feed
nf_feed_type SCP, NRF and SEPP The source NF for the feed
error_reason - The error reason for the failure of the http request sent to the 3rd party application from egress adapter
correlation-id - Taken from correlation-id present in metadata-list.
way - It is taken from the message-direction present in the metadata-list.
srcIP - It is taken from the source-ip present in the metadata-list, Global L3L4 configuration, or in the least priority address configured in the feed.
dstIP - It is taken from the destination-ip present in metadata-list, Global L3L4 configuration, or in the least priority address configured in the feed.
srcPort - It is taken from the source-port present in the metadata-list, Global L3L4 configuration, or in the least priority address configured in the feed.
dstPort - It is taken from the destination-ip present in metadata-list, Global L3L4 configuration, or in the least priority address configured in the feed.
MD - It provides information if the value is taken from metadata-list. It is attached with either srcIP, dstIP. srcPort, or dstPort based on mapping.
LP - It provides information if the value is taken from least priority address configured in the feed. It is attached with either srcIP, dstIP. srcPort, or dstPort based on mapping.
L3L4 - It provides information if the value is taken from the Global L3L4 configuration. It is attached with either srcIP, dstIP. srcPort, or dstPort based on mapping.
The following table includes information about common attributes for OCNADD:

Table 7-2 Attributes

Attribute Description
application The name of the application that the microservice is a part of
microservice The name of the microservice.
namespace The Kubernetes namespace in which microservice is running.
node The name of the worker node that the microservice is running on.
pod The name of the Kubernetes POD.

OCNADD Metrics

The following table lists important metrics related to OCNADD:

Table 7-3 Metrics

Metric Name Description Dimensions
kafka_stream_processor_node_process_total

The total number of records processed by a source node. The metric will be pegged by the aggregation services (SCP, SEPP and NRF) and egress adapter in the data director and denotes the total number of records consumed from the source topic.

Metric Type: Counter
  • application
  • container
  • service
  • namespace
  • processor_node_id
  • task_id
  • thread_id
  • name
  • microservice
kafka_stream_processor_node_process_rate The average number of records processed per second by a source node.

The metric will be pegged by the aggregation services (SCP, SEPP and NRF) and egress adapter in the data director and denotes the records consumed per sec from the source topic.

Metric Type: Gauge
  • application
  • container
  • service
  • namespace
  • processor_node_id
  • task_id
  • thread_id
  • name
  • microservice
kafka_stream_task_dropped_records_total The total number of records dropped within the stream processing task. The metric will be pegged by the aggregation services (SCP, SEPP and NRF) and egress adapter in the data director.

Metric Type: Counter
  • application
  • container
  • service
  • namespace
  • processor_node_id
  • task_id
  • thread_id
  • name
  • microservice
kafka_stream_task_dropped_records_rate

The average number of records dropped within the stream processing task. The metric will be pegged by the aggregation services (SCP, SEPP and NRF) and egress adapter in the data director.

Metric Type: Gauge
  • application
  • container
  • service
  • namespace
  • processor_node_id
  • task_id
  • thread_id
  • name
  • microservice
ocnadd_egress_requests_total

This metric will be pegged as soon as the request reaches the ocnadd egress adapter.

This metric pegs count of total request which has to be forwarded to third party. This metric is used for the Egress MPS at DD.

Metric Type: Counter
  • method
  • instance_identifier
  • nf_feed_type
  • request_type
  • consumer_name
ocnadd_egress_responses_total This metric will be pegged on the Egress adapter when the response is received at egress adapter. This metric is pegged by ocnadd adapter service. This metric pegs count of total responses (success or failed) received from the third party

Metric Type: Counter
  • method
  • status
  • instance_identifier
  • destination_endpoint
  • nf_feed_type
  • request_type
  • consumer_name
ocnadd_egress_failed_request_total

This metric pegs count of total request which are failed to send to third party application. This metric is pegged by egress adapter service

Metric Type: Counter
  • method
  • destination_endpoint
  • consumer_name
  • instance_identifier
  • error-reason
  • nf_feed_type
  • request_type
ocnadd_egress_e2e_request_processing_latency_seconds_bucket The metric is pegged on the egress adapter service. It is the latency between packet timestamp provided by producer NF and egress adapter when the request packet is sent out to the 3rd party application. This latency is calculated for the batch of messages, therefore it is advisable to use the configured batch size of messages for each bucket of processing time for example, the bucket sizes are 10ms, 20ms, 40ms, 80ms, 100ms, 200ms, 500ms, 1000ms and 5000ms and configured batch size is 100 messages, then the count of 10ms bucket should be interpreted as (count_10ms * batch size )

Metric Type: Histogram
  • method
  • instance_identifier
  • quantile(or le)
  • consumer_name
ocnadd_egress_e2e_request_processing_latency_seconds_sum

This is the sum of e2e request processing time for all the requests processed in the batch of messages. It is the latency between packet timestamp provided by producer NF and egress adapter when the packet is sent out. It is the sum of processing time for all the messages in the batch.

Metric Type: Counter
  • method
  • instance_identifier
  • consumer_name
ocnadd_egress_e2e_request_processing_latency_seconds_count

This is the count of batches of messages for which the processing time is summed up. It is the latency between packet timestamp provided by producer NF and egress adapter when the packet is sent out.

Metric Type: Counter
  • method
  • instance_identifier
  • consumer_name
ocnadd_egress_service_request_processing_latency_seconds_bucket

The metric is pegged on the egress adapter service. It is the egress adapter service processing latency and pegged when a request is sent out from egress gateway to the 3rd party application . This latency is calculated for the batch of messages, therefore it is advisable to use the configured batch size of messages for each bucket of processing time for example, the bucket sizes are 10ms, 20ms, 40ms, 80ms, 100ms, 200ms, 500ms, 1000ms and 5000ms and configured batch size is 100 messages, then the count of 10ms bucket should be interpreted as (count_10ms * batch size )

Metric Type: Histogram
  • method
  • instance_identifier
  • quantile(or le)
  • consumer_name
ocnadd_egress_service_request_processing_latency_seconds_sum

The metric is pegged on the egress adapter service. It is the sum of egress adapter service processing latency for the batch of messages and pegged when a request is sent out from egress adapter towards the 3rd party application.

Metric Type: Counter
  • method
  • instance_identifier
  • consumer_name
ocnadd_egress_service_request_processing_latency_seconds_count

The metric is pegged on the egress adapter service. It is the batch count and pegged when a request is sent out from egress adapter towards 3rd party application.

Metric Type: Counter
  • method
  • instance_identifier
  • consumer_name
ocnadd_egress_request_latency_seconds_bucket

The metric is pegged on the egress adapter service. This peg the latency when request reaches adapter and resp is received back from third party. This latency is calculated for the batch of messages, therefore it is advisable to use the configured batch size of messages for each bucket of processing time for example, the bucket sizes are 10ms, 20ms, 40ms, 80ms, 100ms, 200ms, 500ms, 1000ms and 5000ms and configured batch size is 100 messages, then the count of 10ms bucket should be interpreted as (count_10ms * batch size )

Metric Type: Histogram
  • method
  • instance_identifier
  • quantile(or le)
  • consumer_name
ocnadd_egress_request_latency_seconds_sum

The metric is pegged on the egress adapter service. It is the sum of egress adapter request processing latency for the batch of messages and pegged when a response is received back from the 3rd party application by egress adapter.

Metric Type: Counter
  • method
  • instance_identifier
  • consumer_name
ocnadd_egress_request_latency_seconds_count

The metric is pegged on the egress adapter service. It is the batch count and pegged when a response is received back from the 3rd party applicatione by egress adapter.

Metric Type: Counter
  • method
  • instance_identifier
  • consumer_name
ocnadd_adapter_synthetic_packet_generation_count_total

This metric pegs count of synthetic packet generated with either success or failed status.

Metric Type: Counter
  • instance_identifier
  • consumer_name
  • status
  • nf_feed_type
ocnadd_egress_filtered_message_total

This metrics pegs the count of message that is matching with the filter criteria for egress.

Metric Type: Counter
  • service_name
  • filter_name
  • filter_association_type
  • filter_criteria
ocnadd_egress_unmatched_filter_message_total

This metrics pegs the count of message that is not matching with the filter criteria for egress.

Metric Type: Counter
  • service_name
  • filter_name
  • filter_association_type
  • filter_criteria
ocnadd_ingress_filtered_message_total

This metrics pegs the count of message that is matching with the filter criteria for ingress.

Metric Type: Counter
  • service_name
  • filter_name
  • filter_association_type
  • filter_criteria
ocnadd_ingress_unmatched_filter_message_total

This metrics pegs the count of message that is not matching with the filter criteria for ingress.

Metric Type: Counter
  • service_name
  • filter_name
  • filter_association_type
  • filter_criteria
ocnadd_health_total_alarm_raised_total

This metric will be pegged whenever a new alarm is raised to alarm service from Health Monitoring service.

Metric Type: Counter
  • serviceId
  • serviceType
ocnadd_health_total_alarm_cleared_total

This metric will be pegged whenever a clear alarm is invoked from Health Monitoring service.

Metric Type: Counter
  • serviceId
  • serviceType
ocnadd_health_total_active_number_of_alarm_raised_total

This metric will be pegged whenever a raise/clear alarm is raised to alarm service from Health Monitoring service. This denotes the active alarms raised by health monitoring service.

Metric Type: Counter
  • serviceId
  • serviceType
ocnadd_l3l4mapping_info_count

This metric provides details about the references of values taken for the source IP, destination IP, source port, and destination port in synthetic packets.

By Default, it is false. The metric is not pegged, but enabled from the Helm chart. It can be group by checking the number of values mapped with metadata, Global L3L4 configuration, the least priority address.

Metric Type: Counter
  • correlation-id
  • way
  • srcIP
  • dstIP
  • srcPort
  • dstPort
  • MD
  • LP
  • L3L4
ocnadd_ext_kafka_feed_record_total This metric will be pegged by the admin service to provide the total consumed messages by the external Kafka consumer application. The admin service retrieves the consumer offsets count from all the partitions of the aggregated topic and pegs the metric periodically.

Metric Type: Counter

 feed_name