> For the complete documentation index, see [llms.txt](https://docs.fortifiedid.se/access/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortifiedid.se/access/key-components/authenticators/credential-validators/exposed-metrics.md).

# Exposed metrics

Credential validators exposes various metrics depending of the authenticator. The namespace suffix,"ffidAuthnHttp\_" is shared across authenticators. Trailing name depends on the metrics type.

## Metrics type

### Gauges

Each authenticator exposes metric under the initial name space "ffidAuthnHttp\_pending.name.\<authenticator\_id>"

Typically gauges change state when a request is sent and a response is expected back but is not yet received.

### Meters

Meters are registered in tuples. One for failure and one for success. Depending on the authenticator multiple meters may be regisered but always in tuples. The leading namespace is:

* ffidAuthnHttp\_failure.name.\<authenticator\_id>
* ffidAuthnHttp\_success.name.\<authenticator\_id>

### Timers

Authenticator exposing metrics at least one timer. The initial namespace is "ffidAuthnHttp\_request.name.\<authenticator\_id>"


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fortifiedid.se/access/key-components/authenticators/credential-validators/exposed-metrics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.