# gathering metrics on ansible runs

**URL:** <https://forum.ansible.com/t/gathering-metrics-on-ansible-runs/14355>\
**Category:** Ansible Project\
**Created:** [January 15, 2014, 8:48pm UTC](https://forum.ansible.com/t/gathering-metrics-on-ansible-runs/14355 "2014-01-15T20:48:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul\_Sutyrin](https://avatars.discourse-cdn.com/v4/letter/p/9de053/32.png) [@Paul\_Sutyrin](https://forum.ansible.com/u/Paul_Sutyrin)\
**Post date:** [January 15, 2014, 8:48pm UTC](https://forum.ansible.com/t/gathering-metrics-on-ansible-runs/14355/1 "2014-01-15T20:48:07Z")

</div>

Hi folks,

Thanks again for this great new generation tool.

What is the most straightforward way to gather statistics on repeated ansible runs? I plan to configure and deploy many things, unattended tasks also — and have exact picture on how long everything takes.

I would expect some pre/post task hooks that allow me to gather timers (and results/errors too) on per-task basis and report to some Zabbix or Sentry perhaps.

Thanks!

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [January 15, 2014, 8:51pm UTC](https://forum.ansible.com/t/gathering-metrics-on-ansible-runs/14355/2 "2014-01-15T20:51:30Z")

</div>

You could write a callback module, or on the simpler end, just use the “time” command.

---

<div class="post-metadata">

**Author:** ![Paul\_Sutyrin](https://avatars.discourse-cdn.com/v4/letter/p/9de053/32.png) [@Paul\_Sutyrin](https://forum.ansible.com/u/Paul_Sutyrin)\
**Post date:** [January 15, 2014, 8:52pm UTC](https://forum.ansible.com/t/gathering-metrics-on-ansible-runs/14355/3 "2014-01-15T20:52:43Z")

</div>

Thanks Michael!

Callbacks are what I was looking for.

Long live!