GitHubGitHub
Sign upSign in
  • Getting Started
    • Overview
    • 1. Plan analytics update in Avo branch
    • 2. Review changes
    • 3. Request implementation
    • 4. Implement analytics events
    • 5. Validate implementation
    • 6. Merge and Publish
    • What is tracking plan audit?
    • Quickstart: Get your first audit
    • Branch audits
    • Audit rules and configuration
    • Advanced event naming rules
    • What is a tracking plan?
    • Quickstart: Tracking plan in Avo
    • Deep dive: Data design in Avo
      • Overview
      • Journeys
      • Events
      • Properties
      • Metrics
      • Sources
      • Stakeholders
      • Implementation status
      • Workbench
      • Event variants
      • Advanced data design features
      • Quickstart: Branches
      • Approval workflows
      • Branch review screen
      • Review code changes
      • Cross-branch data design
      • Notifications
    • How to collaborate in Avo
      • Defining Descriptive Events and Properties
      • Global Namespace
      • Groups
      • Naming Conventions
      • Agentic data design
      • Archive and Restore
      • Avo as a Solutions Design Document (SDD)
      • Bulk Editing and Use Cases
      • Defining event hierarchy
      • Documenting Downstream Dependencies
      • Documenting Purpose Meetings in Avo
      • Event Triggers and Use Cases
      • Managing Changes Impacting Multiple Stakeholders
      • Multiple sources on Avo branches
      • Name Mapping and Use Cases
      • Object Properties
      • Organizing tracking plans
      • Pinned Properties
      • Reset Tracking Plan
    • Global Requirements
    • Quickstart: Get started with Inspector
    • Inspector Installation Overview
    • Configuring Sources

    • Issues View
    • Events View
    • Debugger View
    • Issue Types
    • Find Issues
    • Fix Issues
    • Ignore Issues
    • Alerts for Slack
    • Import tracking plan from Inspector

    • Inspector GTM integration
    • Inspector Segment integration
    • Inspector RudderStack integration
    • Inspector PostHog integration
    • Inspector Snowplow SDK integration
    • Inspector SDKs
    • Connect Inspector to Adobe Tag Extension
      • Importing Overview
      • Importing a CSV
      • Overview
      • Use Cases
      • Adobe Experience Platform
      • Amplitude Data
      • Mixpanel Lexicon
      • Mparticle Data Master
      • Rudderstack
      • Segment Protocols
      • Snowplow Data Structures
      • Webhook Publishing
    • Exporting
    • Signing and Verifying Webhooks
    • Avo Codegen overview
    • Avo Codegen setup
    • Avo Codegen technical deep dive
    • Quickstart: Avo CLI
      • Avo and Existing Tracking
      • Avo and Git
      • Avo and Linters
      • Avo and Unit Tests
      • Avo in Monorepo
      • Avo in the CI
      • Download or Copy Avo File Manually
      • Explicit Null in Codegen
      • Property Bundles Unbundling
      • Start Implementing Tracking Changes
      • Start Using Inspector with Avo Codegen
      • Start Using Visual Debuggers
    • Members and roles
    • Managing stakeholder
    • Authentication methods
        • Overview
        • Csharp
        • Java
        • JavaScript
        • Kotlin
        • Objc
        • PHP
        • Python
        • Reasonml
        • Rescript
        • Ruby
        • Swift
        • TypeScript
      • Anonymous User Id
      • Custom Loggers
      • Destinations
      • Overview
      • Android
      • Dart
      • Go
      • iOS
      • Java
      • Node
      • React Native
      • Web
      • Overview
      • Mobile
      • Web
      • Overview
      • Authentication
      • Create Branch
      • Export Branch Stats
      • Export Tracking Plan
      • Import Tracking Plan
      • Overview
      • Tools reference
    • Avo Intelligence
    • Inspector Faq
    • Yes You Can Faq
    • Troubleshooting and support
    • Inspector

On This Page

  • Avo Codegen
  • Avo Inspector
Question? Give us feedback →Edit this page
Type safe code, unit tests and CILogs

Logs

Avo Codegen

Avo Codegen functions print logs prefixed with [avo]

Learn about controlling the logs output in Avo Codegen in the reference section.

Avo Inspector

Avo Inspector prints logs prefixed with

[avo] Avo Inspector

Logs are enabled by default in the development environment.

You can enable or disable the logs with the following code:

AvoInspector.setLogging(shouldPrintLogs)
Start Using Visual DebuggersManaging stakeholder

Rescue ringSupport