# Transit Secrets Engine Metrics

**URL:** <https://discuss.hashicorp.com/t/transit-secrets-engine-metrics/29511>\
**Category:** Vault\
**Tags:** vault\
**Created:** [September 15, 2021, 2:30am UTC](https://discuss.hashicorp.com/t/transit-secrets-engine-metrics/29511 "2021-09-15T02:30:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![HunterEl](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/hunterel/32/22350_2.png) [@HunterEl](https://discuss.hashicorp.com/u/HunterEl)\
**Post date:** [September 15, 2021, 2:30am UTC](https://discuss.hashicorp.com/t/transit-secrets-engine-metrics/29511/1 "2021-09-15T02:30:14Z")

</div>

Hey Folks,

Recently stood up an installation of Vault on K8s. We are testing out the Transit Secrets Engine functionality (encryption as a service) for some of our workloads.

Was trying to get some metrics out of it and noticed that no metrics were being emitted around latency for this functionality.

I found [this diff](https://github.com/hashicorp/vault/pull/3985), which has since been closed, which would answer this question.

Curious if there is a plan to support latency metrics for the transit secrets engine or has anyone solved this question in a different way?

Cheers.