S3 archive and monitoring

Company monitoring

The portal's Monitoraggio aziendale link lets direct company administrators review requests, errors, latency, operational logs and traces attributed to their authorized tenants.

Views are read-only and do not expose prompts or chat content. Customers cannot submit arbitrary queries. Members, group managers and reseller administrators without direct company membership do not automatically gain that company's monitoring access.

Queries cover at most seven days and have bounded results. Data begins with attributed telemetry after activation; missing earlier telemetry does not indicate missing accounting usage.

Enable the chat archive

Location: Archivio chat S3. Requires an authorized company administrative role.

1. Prepare an AWS S3 bucket and credentials with the required permissions.
2. Enter bucket, region, prefix and credentials.
3. Keep Maschera i dati personali riconosciuti enabled for pseudonymized exports.
4. Test the destination, save and enable export.
5. Check counters and Ultimi invii after a newly completed request.

The destination test checks bucket access; the first upload also checks prefix permissions. AWS S3 buckets are supported, rather than arbitrary customer-provided endpoints.

Included and excluded content

New completed, settled API and portal exchanges are included, including streams. This is not a historical export. Internal Switchyard classification, interrupted responses, images/audio, signatures and opaque encrypted artifacts are excluded.

With masking, fragments of each SSE channel are joined before detection; original chunk boundaries are not preserved. An unavailable PII service blocks masked delivery. Detection may still miss some personal data.

An oversized event may produce a record with export_error=payload_too_large and no partial text. The archive cannot guarantee every answer if a crash occurs between completion and enqueueing.

Bucket permissions

The credential needs s3:ListBucket on the bucket and s3:PutObject/s3:GetObject on the archive prefix. The application does not require DeleteObject. Avoid broader credentials than necessary.

Files use Zstd-compressed Parquet, required server-side encryption and immutable objects:

PREFIX/tenant_id=UUID/schema_version=1/date=YYYY-MM-DD/hour=HH/part-BATCH_UUID.parquet

The portal provides a DuckDB query to adapt to your destination. Configure credentials in your environment rather than shared query text.

Retention and changes

Queued local payloads expire after 24 hours; delivery metadata remains for 30 days. Customers control retention, access and deletion of received objects.

New settings affect new events. Already queued events retain their original destination, credentials and PII choice. Coordinate rotation before revoking old credentials. Disabling export cancels pending events; an upload already started may complete.