> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/reference/technical-and-support/runtime-and-security/logging-and-monitoring.md).

# Logging and monitoring reference

Distinguish customer-facing execution Monitoring from deeper platform or security telemetry when investigating an operational or technical issue.

There are two different questions that are often called “logging”.

1. **What did this Agent or Workflow execution do?** Use Lleverage [Monitoring](/build-and-improve/monitoring.md).
2. **What platform or security telemetry exists behind the service?** Treat that as a separate technical or assurance question rather than assuming it is exposed in the product UI.

## Customer-facing execution evidence

Monitoring is the current product surface for reviewing execution activity. Depending on the run and your access, it can expose the run record, trace, inputs, outputs, action activity, timings and errors that are available for that execution.

Use it to answer questions such as:

* did the work run;
* where did it stop or fail;
* which actions were performed;
* what inputs and outputs were involved;
* whether the same pattern is recurring across runs.

Monitoring is primarily execution evidence. It should not be described as a complete security audit log, nor should technical success be treated as proof that the operational result was correct.

## Platform and security telemetry

Incident response, forensic review, infrastructure telemetry and retention requirements can require evidence outside the customer-facing Monitoring surface.

Those details can change independently of the UI and may differ by the question being investigated. If an audit or incident depends on specific event coverage, fields or retention, verify that requirement against current Lleverage assurance or support material rather than inferring it from this page.

## When reporting a problem

Capture the smallest useful evidence set: Project, approximate execution time, session or run identifier where available, the observed outcome, and the relevant Monitoring trace. Avoid pasting credentials or secret values into a support message.


---

# 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.lleverage.ai/reference/technical-and-support/runtime-and-security/logging-and-monitoring.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.