> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/references/cli/admin/managedsecrets/logs.md).

# sdm admin managedsecrets logs

```shell
NAME:
   sdm admin managedsecrets logs - display logs for managed secrets

USAGE:
   sdm admin managedsecrets logs [command options] [arguments...]

OPTIONS:
   --json, -j                             output as json
   --timeout value                        set time limit for command
   --filter value                         filter e.g. 'field:name tag:key=value ...'
   --filters-help                         show valid filter strings and examples
   --from value                           begin timestamp (default seven days ago)
   --to value                             end timestamp (default now)
   --output value, --out value, -o value  write log to the specified filename
   --account value, -a value              id
   --secretengine value, --se value       id
   --managedsecret value, --me value      id
   --extended                             include debug information
```


---

# 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.strongdm.com/references/cli/admin/managedsecrets/logs.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.