Guides
Guides

How to access monitoring and metrics in HERE Anonymizer Self-Hosted

Apache Flink metrics

You can access an Apache Flink dashboard at the IP address mapped to jobmanager-ui. For example, you can access the dashboard of a local instance at http://localhost:8081/.

This browser-accessible dashboard offers a large quantity of built-in Flink and Java VM metrics.

See Monitoring Apache Flink Applications for a detailed explanation of existing counters and what the values of these counters can tell you about the health of your Flink application.

Anonymizer metrics

HERE Anonymizer Self-Hosted registers its counters using Flink's metrics system. The following counters are available at the Flink dashboard:

Processing stepMetric nameData objectDescription
DecodingHERE_decoding_message_info_allMessageNumber of messages received and successfully decoded
DecodingHERE_decoding_message_dropped_corruptedMessageNumber of received messages that could not be decoded
DecodingHERE_decoding_chunk_info_allChunkNumber of chunks received and successfully decoded
DecodingHERE_decoding_point_info_allPointNumber of points received and successfully decoded
DecodingHERE_decoding_event_info_allEventNumber of events received and successfully decoded
AnonymizationHERE_cleaning_point_dropped_timestamp_duplicatePointNumber of points dropped because other points duplicated their timestamps in the same trace
AnonymizationHERE_cleaning_point_dropped_invalid_timestampPointNumber of points dropped because their timestamps were ahead of the system clock
AnonymizationHERE_anonymization_trace_info_allTraceNumber of traces reaching the anonymization step
AnonymizationHERE_anonymization_trace_notify_destination_unsuccessfully_obfuscatedTraceNumber of input traces that weren't end cut more than at the last anonymization
AnonymizationHERE_anonymization_trace_unsuccessfully_obfuscatedTraceNumber of input traces that weren't start cut more than required
AnonymizationHERE_anonymization_point_dropped_invalid_timestamp_trace_statePointNumber of points dropped because chunks were received in wrong temporal order
AnonymizationHERE_anonymization_point_dropped_sampling_ratePointNumber of points dropped to adjust the sampling rate to the configured value
AnonymizationHERE_anonymization_point_dropped_startPointNumber of points dropped by start cutting strategy
AnonymizationHERE_anonymization_point_dropped_endPointNumber of points dropped by end cutting strategy
AnonymizationHERE_anonymization_point_dropped_gapPointNumber of points dropped to create a gap in the data
AnonymizationHERE_anonymization_point_dropped_stay_pointPointNumber of points dropped to obfuscate a stay point
AnonymizationHERE_anonymization_point_dropped_zero_speedPointNumber of points dropped due to zero speed
AnonymizationHERE_anonymization_point_dropped_by_other_reasonPointNumber of points dropped for other reasons
AnonymizationHERE_anonymization_point_notify_stay_point_detectedPointNumber of points detected as stay point
AnonymizationHERE_anonymization_point_dropped_originPointNumber of points dropped from origin by origin-destination obfuscation.
AnonymizationHERE_anonymization_point_dropped_destinationPointNumber of points dropped from destination by origin-destination obfuscation
AnonymizationHERE_anonymization_area_notify_stay_point_detectedAreaNumber of areas detected as stay point
AnonymizationHERE_anonymization_area_notify_stay_point_predictedAreaNumber of areas predicted as stay point
AnonymizationHERE_anonymization_point_dropped_chunk_has_too_few_pointsPointNumber of points dropped as number of points in output chunk didn't meet threshold
AnonymizationHERE_anonymization_point_dropped_license_regionsPointNumber of points dropped as they are out of the areas defined by the product license
AnonymizationHERE_anonymization_point_dropped_region_selection_by_exclusionPointNumber of points dropped as they are in the customer-defined excluded regions
AnonymizationHERE_anonymization_point_dropped_region_selection_outside_inclusionPointNumber of points dropped as they are not in the customer-defined included regions
AnonymizationHERE_anonymization_point_dropped_poi_proximityPointNumber of points dropped as they are in the proximity of a sensitive POI
AnonymizationHERE_anonymization_point_info_whitelisted_areaPointNumber of points passed-through because they are in a whitelisted area
AnonymizationHERE_anonymization_event_info_by_type_keepEventNumber of events passed-through because they are configured to be kept
AnonymizationHERE_anonymization_event_dropped_by_type_dropEventNumber of events dropped as they are configured to be dropped
AnonymizationHERE_anonymization_event_dropped_regularEventNumber of events dropped during the anonymization process
AnonymizationHERE_anonymization_point_info_out_of_density_areasPointNumber of points out of the density areas (only if Density-aware anonymization enabled)
OutputHERE_output_message_info_allMessageNumber of messages output by the pipeline
OutputHERE_output_chunk_info_allChunkNumber of chunks output by the pipeline
OutputHERE_output_point_info_allPointNumber of points output by the pipeline
OutputHERE_output_event_info_allEventNumber of events output by the pipeline
OutputHERE_output_webhook_succeedWebhookNumber successful webhook execution notifications. Available only if WEBHOOK_URL is configured.
OutputHERE_output_webhook_failedWebhookNumber of failed webhook execution notification. Available only if WEBHOOK_URL is configured.
ManagementHERE_anonymization_management_events_totalLicense and/or ConfigNumber of update attempts
ManagementHERE_anonymization_management_events_licence_update_attemptsLicenseNumber of license update attempts
ManagementHERE_anonymization_management_events_licence_update_failedLicenseNumber of failed license update attempts
ManagementHERE_anonymization_management_events_config_update_attemptsConfigNumber of config update attempts
ManagementHERE_anonymization_management_events_config_update_failedConfigNumber of failed config update attempts
📘

Note

Management counters are only available if you configured a management queue.

Alert metrics

If any alert configuration is applied, the additional metrics will be available for each defined alert ID.

Processing stepMetric nameData objectDescription
OutputHERE_output_alert_ALERT_ID_message_info_allMessageNumber of messages output by the alert handler with alert ID.
OutputHERE_output_alert_ALERT_ID_chunk_info_allChunkNumber of chunks output by the alert handler with alert ID.
OutputHERE_output_alert_ALERT_ID_point_info_allPointNumber of points output by the alert handler with alert ID.
OutputHERE_output_alert_ALERT_ID_event_info_allEventNumber of events output by the alert handler with alert ID.

AWS metrics

AWS EKS provides a metrics API which offers a set of metrics in the Prometheus format. This means that you can install a Prometheus instance in your Kubernetes cluster and further process the metrics data or watch it using the Prometheus UI.

Additionally, AWS EKS offers a dashboard which shows Kubernetes-level data.

To learn more, see Metrics for Amazon EKS and Kubernetes.

Azure metrics

In Azure, you can use the Azure Monitor to monitor the health and performance of your AKS cluster. The tool offers a variety of charts and counters as well as a Prometheus API.

To learn more, see Monitor AKS with Azure Monitor.