menuOur logging system routes everything through a set of REST-ful API interfaces. This section outlines the interface usedto add logging entries into your application buckets.
Since we are still a new service we do not have wrapper libraries available for all languages. If we do not have a libraryavailable for your programming language you can easily roll your own using these endpoints.
| Name | Required | Description |
|---|---|---|
| Message | Yes | The error message |
| Stack | No | The call stack detailing the flow of the error. |
| Details | No | Any additional details about the error you want to capture. |
| User | No | A user marker or identifier which will allow you to correlate errors to users to assist in troubleshooting. |
| Do Not Track | No | Flag to enable advanced user privacy settings. |
| Name | Required | Description |
|---|---|---|
| Method Name | Yes | The name of the method timings are being logged for. This needs to be unique in the system soif you have multiple methods with the same name you should prefix it with something that makes it unique like the class name. Ex: Customer.Save() or Order.Save() |
| Timing | Yes | How long the method execution took in milliseconds. |
| User | No | A user marker or identifier which will allow you to correlate possible performance issues to individual users. |
| Do Not Track | No | Flag to enable advanced user privacy settings. |
| Name | Required | Description |
|---|---|---|
| Event Name | Yes | The name of the event you are tracking. This needs to be unique across events, so if you are logginga common event, such as page load, you need to prefix it with something unique like the page name. Ex: Home.Load or Products.Load |
| Details | No | Any additional details you want to capture about the event or action. |
| User | No | A user marker or identifier which will allow you to correlate events to specific users in your system. |
| Do Not Track | No | Flag to enable advanced user privacy settings. |
| Name | Required | Description |
|---|---|---|
| Method | Yes | The name of the method being traced. |
| Details | Yes | The message indicating the information you want to log. |
| User | No | A user marker or identifier which will allow you to correlate the information being logged to specific users. |
| Do Not Track | No | Flag to enable advanced user privacy settings. |
| Name | Required | Description |
|---|---|---|
| Name | Yes | The name of the action. |
| Interval | Yes | The interval of time for the collection. Defaults to 60 seconds. |
| Count | Yes | The number of actions which were executed during the interval. |
| Timestamp | No | The starting timestamp of the action interval. |
| Process Identifier | No | If multiple processes are executing on a single server you can track the identifier so you can see the actions broken down by process. |
| Min Timing | No | Allows you to track the minimum execution time for the action (in milliseconds) |
| Max Timing | No | Track the maximum execution time for the action (in milliseconds) |
| Total Timing | No | The total timing of all the actions logged in this interval. Used to calculate the average over time. |
In addition to the standard values listed above you can also extend your posts with additional information as necessary. Simply add inanother object property for a POST submission or another query string parameter for a GET drop.
The values you add are stored with the individual item instances and can be later used as additional filter parameters or to give additionalcontext to the stored information.
The following values are automatically appended to your submissions so you do not, and should not, add them to your submissions.