Logging & Diagnostics

Aurono maintains detailed logs of its operation.

Logging exists to make Aurono:

Transparent
Auditable
Debuggable
Predictable

This page explains why logs exist, what they contain, and how to use them.

Why Aurono Uses Logging

Aurono is a deterministic execution engine.

Logging ensures that:

Every action can be explained
Every decision can be traced
Unexpected behavior can be diagnosed
Strategy execution can be audited afterward

Logs are not an afterthought.
They are a core part of Aurono’s design.

What Aurono Logs

Aurono logs events, not opinions.

Examples of logged events include:

Strategy evaluation cycles
Candle data used for evaluation
Buy and sell trigger checks
Capital availability checks
Order construction (price and amount)
Order submission to the exchange
Exchange order status updates
Actual fill prices and amounts
Allocation corrections
Strategy state updates

Aurono does not log:

API secrets
Private keys
Personal user data

Log Levels (Conceptual)

Aurono logs information at different conceptual levels:

Informational — normal operation
Execution — orders and fills
Warnings — skipped actions or constraints
Errors — failed operations or external issues

Most users will see primarily informational and execution logs.

Where to View Logs

Dashboard View

The Aurono dashboard surfaces high-level activity:

Executed trades
Skipped actions
Strategy updates

This view is designed for everyday monitoring, not deep debugging.

Device Logs (Advanced)

For deeper inspection, Aurono maintains local log files on the device.

These logs include:

Full execution flow
Exchange responses
Internal decision points

They are intended for:

Advanced users
Troubleshooting
Support diagnostics

How to Use Logs Effectively

Logs answer questions such as:

Why didn’t a trade execute?
Which candle was evaluated?
What price was used for the limit order?
Was capital available at the time?
Did the exchange fill the order?
Was a safeguard triggered?

Logs describe what happened, not what should have happened.

Example Log Flow (Buy)

A typical buy cycle may include entries such as:

Strategy evaluation started
Candle loaded (timeframe, open, close)
Buy trigger condition evaluated
Capital availability confirmed
Limit price calculated
Order sent to exchange
Order filled
Allocation corrected
Strategy state updated

Each step is logged in sequence.

Example Log Flow (Skipped Trade)

A skipped trade is also logged, for example:

Buy trigger met
Insufficient allocated capital
Order not placed

This ensures skipped actions are visible and explainable.

Logging and Determinism

Logs are especially important because Aurono is deterministic.

Given:

The same configuration
The same market data

Aurono will:

Make the same decisions
Generate the same logs

This makes behavior reproducible and auditable.

When to Check Logs

Check logs if:

A trade did not occur when expected
A strategy appears inactive
An exchange connection failed
You are troubleshooting configuration issues

Logs are often more precise than dashboard summaries.

When Logs Indicate Normal Behavior

Many log entries indicate expected outcomes, such as:

Conditions not met
Safeguards preventing execution
Precision constraints blocking orders

These are not errors.

If you contact support, logs help diagnose issues quickly.

When sharing logs:

Include the relevant timeframe
Include the strategy involved
Do not share API keys or secrets

Aurono logs are designed to be shareable without exposing sensitive data.

Key Takeaway

Logs exist to explain Aurono’s behavior.

If something did not happen:

The logs will show why
The explanation will be deterministic
The outcome will match configuration and safeguards

Aurono logs actions — not assumptions.

Trading Engine — How Aurono Executes Trades
Precision, Rounding & Exchange Constraints
Why Aurono Uses Limit Orders Only
Troubleshooting