Ticket

A Ticket is a collection of equal Incidents submitted by one or more application instances. A ticket can aggregate a certain amount of Incidents, determined by a Quotation Profile (see Project Management Guide - additional incoming incidents are dropped.

You can inspect the received Tickets of a registered project using the Ticket Overview Page available on the Project Management Section of your account.

Incident

Incoming application incident reports are stored as Incidents. Incidents are basicly just a bunch of Properties and binary Attachments.

Properties

Properties are the meat and bones of an Incident as they store the actual application incident details. Properties are string key-value pairs, stating the operation system, application version, a message string, the stacktrace etc.

Every incident consists of a number of mandatory Properties (Message, Project Name, Project version, Occurance Date and Reporting Date) and optional further Properties. The maximum amount of additional properties is determined by the active Quotation Profile (see Project Management Guide. Exceeding Properties will be dropped. A Property`s key length is limited to 32 characters, the corresponding value is limited to 1024 characters - if these length restrictions are violated, the violating string gets trimmed.

Example property: os.name=windows 2000.

Attachments

Attachments are (optional) binary attachments to incident reports. These attachments could carry images, log files or whatever is interesting in the context of an application incident.

The number of Attachments per Incident is not limited but the overall binary size - it is determined by the active Quotation Profile which usally grants between 10Kb and 100Kb.

Quotation example: if an incident comes with 4 attachments (1Kb, 3 Kb, 5 Kb and 7 Kb) and your Attachment quota is 10 Kb, the first 3 attachments are stored while the 4th is dropped as it exceeds the accumulated attachment size.