Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
Meridian-2019.1.18, Meridian-2020.1.7, 27.1.1
-
Security Level: Default (Default Security Scheme)
-
NB
Description
When enabling the evaluation layer, that feature creates a log file called EvaluationMetrics.log with the values from the counters required to perform a persistence layer evaluation.
Of course, this happens only when having Telemetryd enabled in service-configuration.xml. If you disable it, the unwanted counters are not present.
Here is an example of the expected content:
2021-05-07 13:46:50,653 INFO [metrics-logger-reporter-1-thread-1] EvaluationMetrics: type=GAUGE, name=evaluate.groups, value=82 2021-05-07 13:46:50,653 INFO [metrics-logger-reporter-1-thread-1] EvaluationMetrics: type=GAUGE, name=evaluate.interfaces, value=8 2021-05-07 13:46:50,654 INFO [metrics-logger-reporter-1-thread-1] EvaluationMetrics: type=GAUGE, name=evaluate.nodes, value=0 2021-05-07 13:46:50,654 INFO [metrics-logger-reporter-1-thread-1] EvaluationMetrics: type=GAUGE, name=evaluate.numeric-attributes, value=287 2021-05-07 13:46:50,654 INFO [metrics-logger-reporter-1-thread-1] EvaluationMetrics: type=GAUGE, name=evaluate.resources, value=44 2021-05-07 13:46:50,654 INFO [metrics-logger-reporter-1-thread-1] EvaluationMetrics: type=GAUGE, name=evaluate.string-attributes, value=66 2021-05-07 13:46:50,656 INFO [metrics-logger-reporter-1-thread-1] EvaluationMetrics: type=METER, name=evaluate.samples, count=10854, mean_rate=8.614191587123628, m1=8.993287964895432, m5=8.694628203336677, m15=6.564777659036456, rate_unit=events/second
Unfortunately, somehow, some Telemetry counters appear on that log file, and those don't belong there because they have nothing to do with the evaluation layer.
I'm attaching a sample log for reference.
Attachments
Issue Links
- mentioned in
-
Page Loading...
