# Tracking the lifecycle (creations, modifications) of visualizations and dashboards

**URL:** <https://discuss.elastic.co/t/tracking-the-lifecycle-creations-modifications-of-visualizations-and-dashboards/134248>\
**Category:** Kibana\
**Created:** [June 1, 2018, 3:17pm UTC](https://discuss.elastic.co/t/tracking-the-lifecycle-creations-modifications-of-visualizations-and-dashboards/134248 "2018-06-01T15:17:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kennethnanwu](https://avatars.discourse-cdn.com/v4/letter/k/e36b37/32.png) [@kennethnanwu](https://discuss.elastic.co/u/kennethnanwu)\
**Post date:** [June 1, 2018, 3:17pm UTC](https://discuss.elastic.co/t/tracking-the-lifecycle-creations-modifications-of-visualizations-and-dashboards/134248/1 "2018-06-01T15:17:50Z")

</div>

Hello,

I am wondering if it is possible to change the way Kibana stores all the visualizations and dashboards? basically, I want to know when and who the visualizations and dashboards get created, as well as when they get modified. And for the 'who', we are using SearchGuard so I should be able to get the current user's name.  
the question is: is it possible to make kibana stores extra information in the .kibana index?

---

<div class="post-metadata">

**Author:** ![Bill\_McConaghy](https://avatars.discourse-cdn.com/v4/letter/b/ed655f/32.png) [@Bill\_McConaghy](https://discuss.elastic.co/u/Bill_McConaghy)\
**Post date:** [June 1, 2018, 4:55pm UTC](https://discuss.elastic.co/t/tracking-the-lifecycle-creations-modifications-of-visualizations-and-dashboards/134248/2 "2018-06-01T16:55:30Z")

</div>

This would require coding this behavior in your own fork of Kibana at the moment. It does not support auditing of edits as you want. You might also put in a request for enhancement at the Kibana github repo. [https://www.github.com/elastic/kibana](https://www.github.com/elastic/kibana)

---

<div class="post-metadata">

**Author:** ![kennethnanwu](https://avatars.discourse-cdn.com/v4/letter/k/e36b37/32.png) [@kennethnanwu](https://discuss.elastic.co/u/kennethnanwu)\
**Post date:** [June 1, 2018, 7:34pm UTC](https://discuss.elastic.co/t/tracking-the-lifecycle-creations-modifications-of-visualizations-and-dashboards/134248/3 "2018-06-01T19:34:25Z")

</div>

Thank you for your quick response!

---

<div class="post-metadata">

**Author:** ![nkoothrappahli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nkoothrappahli/32/31959_2.png) [@nkoothrappahli](https://discuss.elastic.co/u/nkoothrappahli)\
**Post date:** [June 6, 2018, 12:11pm UTC](https://discuss.elastic.co/t/tracking-the-lifecycle-creations-modifications-of-visualizations-and-dashboards/134248/4 "2018-06-06T12:11:35Z")

</div>

When you already have Search Guard in place you can use the auditlog to track changes to the .kibana index.

> **[Configuring Audit Logging | Search Guard | Security for Elasticsearch](https://docs.search-guard.com/latest/audit-logging-compliance)**
>
> Implement Audit Logging on your Elasticsearch cluster and stay compliant with GDPR, HIPAA, ISO, PCI and SOX.

---

<div class="post-metadata">

**Author:** ![kennethnanwu](https://avatars.discourse-cdn.com/v4/letter/k/e36b37/32.png) [@kennethnanwu](https://discuss.elastic.co/u/kennethnanwu)\
**Post date:** [June 6, 2018, 2:09pm UTC](https://discuss.elastic.co/t/tracking-the-lifecycle-creations-modifications-of-visualizations-and-dashboards/134248/5 "2018-06-06T14:09:25Z")

</div>

This is super helpful! Thank you soooo much, Nanda!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 4, 2018, 2:09pm UTC](https://discuss.elastic.co/t/tracking-the-lifecycle-creations-modifications-of-visualizations-and-dashboards/134248/6 "2018-07-04T14:09:29Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.