Logging the output for every start and success of every metricset within AutoOps has proven to be extremely noisey and wasteful.
Users that are interested in determining this information without enabling debug logging can, in Metricbeat, use logging.metrics.period. For OTel users using AutoOps via the metricbeatreceiver, you can scrape this information dynamically from the Prometheus endpoint (running at http://agent-host:8888/metrics), like:
$ curl http://localhost:9999/metrics | grep _log_records
Logging the output for every start and success of every metricset within AutoOps has proven to be extremely noisey and wasteful.
Users that are interested in determining this information without enabling debug logging can, in Metricbeat, use
logging.metrics.period. For OTel users using AutoOps via themetricbeatreceiver, you can scrape this information dynamically from the Prometheus endpoint (running athttp://agent-host:8888/metrics), like:$ curl http://localhost:9999/metrics | grep _log_records