# Audit log study

**URL:** <https://discuss.elastic.co/t/audit-log-study/167613>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [February 8, 2019, 11:22am UTC](https://discuss.elastic.co/t/audit-log-study/167613 "2019-02-08T11:22:51Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\
**Post date:** [February 11, 2019, 8:44am UTC](https://discuss.elastic.co/t/audit-log-study/167613/8 "2019-02-11T08:44:19Z")

</div>

> [@Elango-mas](#):
>
> I don't understand, what do you by "You don't need to do this."

I'm really not sure what is unclear from the answers above. I will restate that:

- the audit logging is not configured in `log4j2.properties`.
- the audit logging is configured in `elasticsearch.yml`.
- we have detailed documentation on how to control what gets written in the audit log, but you need to read the documentation. I have linked to it.

> [@Elango-mas](#):
>
> If this not the way to control the verbosity, then how can I.

I have shared the link to our documentation that describes everything and answers your questions 2 times already in the posts above. Once more: [Auditing Security Events | X-Pack for the Elastic Stack [6.2] | Elastic](https://www.elastic.co/guide/en/x-pack/current/auditing.html#audit-log-settings)

> [@Elango-mas](#):
>
> Or is there no verbose output in audit log?

There is no "VERBOSE" or "DEBUG" or "TRACE" level audit logging if that's what you want. This is _not_ how you control the audit logs, _please_ read the docs.

---

_[View the full topic](https://discuss.elastic.co/t/audit-log-study/167613)._