> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avigrah.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring & Logs

Avigrah provides built-in monitoring and logging to ensure transparency, traceability, and operational visibility across all AI workflows.

This allows organizations to understand how systems behave, how workflows execute, and how actions are performed over time.

***

### What is Logged

Avigrah captures structured logs across key system activities, including:

* AI task executions and workflow runs
* Integration activity with external systems
* System-level events and operational signals
* User-triggered actions and automation events

Logs are designed to provide visibility into **what was executed, when it occurred, and system-level outcomes**.

***

### Pipeline Execution Logs (Dedicated View)

Data pipeline executions are handled within a dedicated **Pipeline Execution Engine**.

* Detailed pipeline logs (ingestion, transformation, storage, vectorization)
* Phase-by-phase execution tracking
* Status monitoring for each pipeline run

These logs are **not part of the generic Monitoring & Logs view**.

To maintain clarity and usability:

* Pipeline-specific logs are accessible only within the pipeline execution interface
* The Monitoring & Logs page provides a high-level, cross-system view

This separation ensures focused debugging for pipelines while keeping overall system monitoring clean and accessible.

***

### Purpose of Logging

Logging in Avigrah supports:

* Monitoring execution health and system performance
* Debugging and issue resolution
* Auditability of workflows and actions
* Operational transparency across teams

Logs are designed for **traceability and governance**, not raw data exploration.

***

### Access Control

Log visibility is governed by roles and scoped permissions.

* **Organization Admins and Owners** have broader visibility across system activity
* **Project-level users** can access logs related only to projects they are part of
* Users can only view logs within their authorized scope

This ensures that access to logs aligns with responsibility and data boundaries.

***

### Scope of Visibility

Logs are scoped across multiple levels:

* Organization-level activity (for authorized roles)
* Project-specific executions and workflows
* User-level actions within assigned environments

Cross-project or cross-organization access is restricted by design.

***

### Data Sensitivity

Logs primarily capture **execution metadata**, not full raw datasets.

* Inputs and outputs may be partially logged where required for traceability
* Sensitive data handling follows organization-level policies and configurations

Avigrah is designed to balance **observability with data protection**.

***

### Retention & Availability

Log availability depends on:

* System configuration
* Infrastructure constraints
* Contractual agreements

Logs are accessible within the defined retention window for the organization.

***

### Evolving Capabilities

Monitoring and logging capabilities in Avigrah continue to evolve.

This includes improvements in:

* Real-time monitoring
* Log granularity and filtering
* Audit and compliance tooling

Access patterns, visibility scopes, and logging depth may be updated over time to improve performance, usability, and governance.

***

### Key Principle

Avigrah provides **controlled visibility with strict access boundaries**.

* Logs enable accountability
* Access is permissioned
* Visibility is scoped and structured

This ensures organizations maintain operational awareness without compromising security or data integrity.