Email Notifications

The Broadsign Server can send email notifications to you and your staff when events occur on your network.

You can opt in and opt out of notifications for network status changes (connected, disconnected, MIA), incidents of all types and when changes are made to campaigns, ad copies and registrations.

Broadsign can detect various incident types, and gather them into the Incident Report.

Email notifications are sent by the Broadsign Server to registered contacts.

By adding a Contact to a display unit, player or edge server, that contact will only receive notifications pertaining to that particular resource.

However, by adding a contact to the domain, that contact will receive all notifications pertaining to all resources in the entire network.

Contacts can choose which types of notifications to receive in the Notification Tab of the Contact Properties Dialog.

To receive SMS notification on a cell phone, simply configure a contact with the SMS gateway email address of the desired phone. The gateway email address can be provided by your cellphone service provider (if this service exists).

Player Contacted Server

There are two possible states for a monitored Broadsign Player. The first is registered to the server (service started). This Player has registered for monitoring with the server (sample email body below).

Subject Player 11537 Contacted Server
Body 2015-05-25T16:57:33
Id: 11537
Name: Player 11537 – DT40 San Francisco
Status: Registering to server.
Action: Turning on monitoring.
IP Address: 62.107.129.248
Private IP Address: 192.168.35.128
Domain: DigitalSign
Player Shutting Down

The second is unregistered from the server (service stopped). This Player has been shut off properly (sample email body below).

Subject Player 11537 Shutting Down
Body 2015-04-26T20:53:25
Id: 11537
Name: Player 11537 – DT40 San Francisco
Status: Unregistering from server.
Action: Turning off monitoring.
IP Address: 62.107.129.42
Private IP Address: 192.168.35.128
Domain: DigitalSign
Edge Server Contacted Server

Similarly to a Player, an email notification is received when a Edge Server connects to the server. This Edge Server has registered for monitoring with the server.

Subject Edge Server 75998 Contacted Server
Body 20 Jun 2015 17:04:05 (UTC)
Id: 75998
Type: Edge Server
Status: Registering to server.
Action: Turning on monitoring.
Name: 192.168.28.237
IP Address: 192.168.28.237
Private IP Address: 192.168.28.237
Domain: DigitalSign
Edge Server Shutting Down
Subject Edge Server 75998 Shutting Down
Body 20 Jun 2015 17:04:05 (UTC)
Id: 75998
Type: Edge Server
Status: Unregistering from server.
Action: Turning off monitoring.
Name: 192.168.28.237
IP Address: 192.168.28.237
Private IP Address: 192.168.28.237
Domain: DigitalSign
Difficulties Polling

When a Player is not sending complete data to the Server during its polling you will be notified of an incident as follows.

Subject Player 2935095 – Incident 400445 Reported: Difficulties Polling
Body Id: 2935095
Name: TR # 30 – Player Windows XP
Type: Player
IP Address: 192.168.28.230
Private IP Address: 192.168.28.230
Domain: DigitalSign
Problematic Resource Id: 2935095
Incident Id: 400445
Incident Type: Difficulties Polling
Problem Description: Player 2935095 is having difficulties polling.
Missing Responses: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30.
Reported On: 25 Feb 2015 23:10:56 (UTC)
Player MIA

Whenever a Player has gone Missing in Action (MIA), an incident will be generated. The incident email for an MIA looks as follows:

Subject Player 574 – Incident 100871 Reported: MIA
Body Id: 574
Name: DT41 San Francisco
Type: Player
IP Address: 192.168.28.247
Private IP Address: 192.168.28.247
Domain: DigitalSign
Incident Id: 100871
Incident Type: MIA
Problem Description: Has not polled since 12 Jun 2015 14:44:20 (UTC).
Reported On: 12 Jun 2015 15:29:34 (UTC)

As you can see, this email allows you to determine which Player has gone MIA, the last time that the system polled, and the reported time of the incident. When the MIA incident has been resolved, all of this Player’s contacts will receive an email notifying them that it has been resolved.

Subject Player 574 – Incident 100871 Resolved: MIA
Body Id: 574
Name: DT41 San Francisco
Type: Player
IP Address: 192.168.28.247
Private IP Address: 192.168.28.247
Domain: DigitalSign
Incident Id: 100871
Incident Type: MIA
Problem Description: Has not polled since 12 Jun 2015 14:44:20 (UTC).
Reported On: 12 Jun 2015 15:29:34 (UTC)
Resolved Description: Contacted Server.
Resolved On: 12 Jun 2015 15:31:22 (UTC)
Unexpected Shutdown

Unexpected Shutdown incidents occur when a Player is forced to shut down by abnormal means, whether it is through manual intervention, such as the machine being shut down by using its Master Power switch or Reset button, or through unforeseen circumstances, such as a power outage. In such a case, you will receive an email similar to the one below. There is no ‘Reported’ incident notification for this type since as soon as it is reported it can safely be resolved.

Subject Player 15285 – Incident 7223 Resolved: Unexpected Shutdown
Body Id: 15285
Name: DT41 San Francisco
Type: Player
IP Address: 192.168.28.247
Private IP Address: 192.168.28.247
Domain: DigitalSign
Incident Id: 7223
Incident Type: Unexpected Shutdown
Problem Description: Unexpected Shutdown
Reported On: 12 Jun 2015 15:29:34 (UTC)
Resolved Description: The application was restarted.
Resolved On: 12 Jun 2015 15:31:22 (UTC)

As you can see, this email allows you to determine which Player has shut down unexpectedly, as well as how the incident was resolved.

Edge Server MIA

The only type of Edge Server incident possible involves a system going Missing in Action (MIA). Whenever a Edge Server has gone MIA, an incident will be generated. An MIA incident email looks as follows:

Subject Edge Server 97498 – Incident 102836 Reported: MIA
Body Id: 97498
Name: 192.168.28.118
Type: Edge Server
IP Address: 192.168.28.118
Private IP Address: 192.168.28.118
Domain: DigitalSign
Problematic Resource Id: 97498
Incident Id: 102836
Incident Type: MIA
Problem Description: Has not polled since 07/20/15 15:02:39 (UTC).
Reported On: 20 Jun 2015 15:49:00 (UTC)

As you can see, this email allows you to determine which Edge Server has gone MIA, the last time that the system polled, and the reported time of the incident. When the MIA incident has been resolved, all of the Edge Server’s contacts will receive an email notifying them that the MIA incident has been resolved.

Subject Edge Server 97498 – Incident 102836 Resolved: MIA
Body Id: 97498
Name: 192.168.28.118
Type: Edge Server
IP Address: 192.168.28.118
Private IP Address: 192.168.28.118
Domain: costa
Incident Id: 102836
Incident Type: MIA
Problem Description: Has not polled since 07/20/15 15:02:39 (UTC).
Reported On: 20 Jun 2015 15:49:00 (UTC)
Resolved Description: Contacted Server.
Resolved On: 20 Jun 2015 16:02:39 (UTC)
Playback Error

When a playback error of a particular ad occurs, an incident is generated and an email notification is sent. The email will be similar to the one below:

Subject Player 574 – Incident 100812 Reported: Playback – Error
Body Id: 574
Name: DT41 San Francisco
Type: Player
IP Address: 192.168.28.247
Private IP Address: 192.168.28.247
Domain: DigitalSign
Incident Id: 100812
Incident Type: Playback – Error
Problem Description: Could not find an appropriate codec for content id 74602
Reported On: 11 Jun 2015 18:49:27 (UTC)

From the message above, we can gather that a playback error of content ID 74602 has occurred on Player ID 574. The playback error occurred either because missing codecs or the fact that the content is not supported.

Missing Ad Copy

A missing ad copy incident will be generated when a Player does not have a local copy of the Ad Copy currently scheduled to play. The message that will be sent out will look as follows:

Subject Player 90002 – Incident 100869 Reported: Playback – Missing Ad Copy
Body Id: 90002
Name: DT42 San Francisco
Type: Player
IP Address: 192.168.28.203
Private IP Address: 192.168.28.203
Domain: DigitalSign
Incident Id: 100869
Incident Type: Playback – Missing Ad Copy
Problem Description: Missing content file for content id 92833
Reported On: 12 Jun 2015 15:02:52 (UTC)

Upon receiving this message, you will be able to see that Player ID 90002 is supposed to play content ID 92833, but that the Player has not downloaded the content. This could mean that the download is not complete. Viewing the Player’s Download Report allows you to gather more information on the content’s download progress. Once the system is able to display the ad copy successfully, the incident will be resolved, and a notification will be sent to all contacts. For more information about the download report, see Download Report.

The email notification will look as follows:

Subject Player 90002 – Incident 100869 Resolved: Playback – Missing Ad Copy
Body Id: 90002
Name: DT42 San Francisco
Type: Player
IP Address: 192.168.28.203
Private IP Address: 192.168.28.203
Domain: DigitalSign
Problematic Resource Id: 92833
Incident Id: 100869
Incident Type: Playback – Missing Ad Copy
Problem Description: Missing content file for content id 92833
Reported On: 12 Jun 2015 15:02:52 (UTC)
Resolved Description: Content id 92833 now available.
Resolved On: 12 Jun 2015 15:06:17 (UTC)
Truncated Ad Copy

A Truncated Ad Copy incident occurs when the ad copy’s duration (the duration must be explicitly specified in the Administrator) is greater than the reserved slot duration. In such a case, you will receive an email similar to the one below:

Subject Player 56890 – Incident 89790 Reported: Playback – Truncated Ad Copy
Body Id: 56890
Name: DT43 San Francisco
Type: Player
IP Address: 192.168.28.196
Private IP Address: 192.168.28.196
Domain: DigitalSign
Problematic Resource Id: 56856
Incident Id: 89790
Incident Type: Playback – Truncated Ad Copy
Problem Description: Truncated content file for bundle id 56856.
Reported On: 21 Jun 2015 22:09:04 (UTC)

Once the incident has been resolved, contacts will be notified accordingly.

Subject Player 56890 – Incident Resolved: Playback – Truncated Ad Copy
Body Id: 56890
Name: DT43 San Francisco
Type: Player
IP Address: 192.168.28.196
Private IP Address: 192.168.28.196
Domain: DigitalSign
Problematic Resource Id: 56856
Incident Id: 89790
Incident Type: Playback – Truncated Ad Copy
Problem Description: Truncated content file for ad copy 56856.
Reported On: 06/21/15 22:09:04 (UTC)
Resolved Description: Ad copy 56856 no longer truncated.
Resolved On: 22 Jun 2015 23:27:27 (UTC)
Disk Space Error

A Disk Space Error is created by the Player when its hard drive becomes full and it is forced to delete content that it is currently scheduled to play to continue its operation. In such a case, you will receive an email similar to the one below:

Subject Player 1789920 – Incident 322585 Reported: Playback – Disk Space Error
Body Id: 1789920
Name: DT43 San Francisco
Type: Player
IP Address: 192.168.28.196
Private IP Address: 192.168.28.196
Domain: DigitalSign
Problematic Resource Id: 630211
Incident Id: 322585
Incident Type: Playback – Disk Space Error
Problem Description: The ad copy 630211 was deleted from disk to free some space although it is currently still in use.
Reported On: 21 Jun 2015 22:09:04 (UTC)

Once the incident has been resolved, contacts will be notified accordingly.

Subject Player 1789920 – Incident 322585 Resolved: Playback – Disk Space Error
Body Id: 1789920
Name: DT43 San Francisco
Type: Player
IP Address: 192.168.28.196
Private IP Address: 192.168.28.196
Domain: DigitalSign
Incident Id: 322585
Incident Type: Playback – Disk Space Error
Problem Description: The ad copy 630211 was deleted from disk to free some space although it is currently still in use.
Reported On: 21 Jun 2015 22:09:04 (UTC)
Resolved Description: The ad copy 630211 was successfully downloaded
Resolved On: 22 Jun 2015 23:27:27 (UTC)
Not Full Screen

If a Player is set to start in full screen mode and it exits that mode via some user intervention a Not Full Screen incident is created. When the Not Full Screen incident is generated, all contacts will receive the following email notification:

Subject Player 90002 – Incident 100870 Reported: Display – Not Full Screen
Body Id: 90002
Name: DT42 San Francisco
Type: Player
IP Address: 192.168.28.203
Private IP Address: 192.168.28.203
Domain: DigitalSign
Incident Id: 100870
Incident Type: Display – Not Full Screen
Problem Description: Full screen off.
Reported On: 12 Jun 15 15:03:47 (UTC)

The Broadsign Suite has a feature implemented that allows a Player to start in full screen mode, or even in minimized mode. If the Player starts in minimized mode, an incident will be generated, and an email notification will be sent. When someone maximizes the Player, the incident will be solved, and the following email notification will be sent to the relevant contacts:

Subject Player 90002 – Incident 100870 Resolved: Display – Not Full Screen
Body Id: 90002
Name: DT42 San Francisco
Type: Player
IP Address: 192.168.28.203
Private IP Address: 192.168.28.203
Domain: DigitalSign
Incident Id: 100870
Incident Type: Display – Not Full Screen
Problem Description: Full screen off.
Reported On: 12 Jun 2015 15:03:47 (UTC)
Resolved Description: Full screen on
Resolved On: 22 Jun 2015 23:27:27 (UTC)
Device Error

The device error incident is caused by a device operation causing an error. When this type of incident occurs, the following information will be sent to all relevant contacts:

Subject Player 682 – Incident 89880 Reported: Display – Device Error
Body Id: 682
Name: DT44 San Francisco
Type: Player
IP Address: 192.168.27.213
Private IP Address: 192.168.27.213
Domain: daniels
Problematic Resource Id: 3077112
Incident Id: 403617
Incident Type: Display – Device Error
Problem Description: Problem with display device. Action “assert_power”, value 1 failed on COM port “com_port1”. The Device Opcode Id of the failed action is 3077112.
Command sent: “020503”
Expected response: “06”
Actual response: nothing
Reported On: 2/29/2015 5:46:52 PM (UTC)

When a contact receives this email, he will be informed that a device control operation has caused an error on Player ID 682. The error was caused while executing an Assert Power operation; each device error incident will have a description of the error’s cause within it. This type of incident will indicate to the appropriate contacts that the Player’s screen is turned off. Once the incident is resolved, in this case, by turning the screen on, a resolved notification will be sent to the contacts.

Subject Player 682 – Incident 89880 Resolved: Display – Device Error
Body Id: 682
Name: DT44 San Francisco
Type: Player
IP Address: 192.168.28.241
Private IP Address: 192.168.28.241
Domain: DigitalSign
Incident Id: 89880
Incident Type: Display – Device Error
Problem Description: Problem with display device. Action “assert_power” failed.
Reported On: 22 Jun 2015 07:08:03 (UTC)
Resolved Description: Action “assert_power” succeeded.
Resolved On: 22 Jun 2015 14:09:20 (UTC)
Performance Problem

In the Administrator, a user can edit a Configuration Profile to set incident thresholds for CPU performance (the default values are 90% of CPU for over 15 seconds). If a Player exceeds these defined thresholds, an incident will be reported by the Player and a notification will be sent out by the server. This type of incident is indicative that a Player is playing content that is beyond its hardware capabilities (e.g.: too many videos playing simultaneously, high definition content on an under-powered machine, etc.).

The Player cannot resolve this incident on its own. It must be manually resolved in the Administrator. No notification is sent when an incident is resolved manually.

Subject Player 436 – Incident 400448 Reported: Performance Problem
Body Id: 436
Name: TR – #18 – Ubuntu
Type: Player
IP Address: 192.168.28.218
Private IP Address: 192.168.28.218
Domain: DigitalSign
Incident Id: 400448
Incident Type: Performance Problem
Problem Description: The system has encountered a performance problem.The CPU usage threshold of 30% over 60 seconds has been exceeded.
CPU Usage [current/average]: CPU 0 [99%/30%]
Reported On: 25 Feb 2015 23:40:19 (UTC)
Domain Quota Exceeded

In the event you exceed your domain quota, you will be notified via e-mail as follows:

Subject Domain 1882067 – Incident 402759 Reported: Domain Quota Exceeded
Body Id: 1882067
Name: TR – #18 – Ubuntu
Type: Domain
IP Address: Not Available.
Private IP Address: Not Available.
Domain: DigitalSign
Problematic Resource Id: 1882067
Incident Id: 402759
Incident Type: Domain Quota Exceeded
Problem Description: Quota is exceeded by 341663635 bytes for domain Id 1882067.
Reported On: 2/28/2015 4:07:10 PM (UTC)
Archived Ad Copy

When you have exceeded your domain quota and Ad Copies are archived you will receive the following notification:

Subject Domain 1882067 – Incident 413697 Resolved: Domain Quota Exceeded
Body Id: 1882067
Name: TR – #18 – Ubuntu
Type: Domain
IP Address: Not Available.
Private IP Address: Not Available.
Domain: DigitalSign
Problematic Resource Id: 1882067
Incident Id: 413697
Incident Type: Domain Quota Exceeded
Problem Description: Quota is exceeded by 396920384 bytes for domain Id 1882067.
Reported On: 11 Mar 2015 15:39:05 (UTC)
Resolved Description: The following 1 inactive or least recently used content(s) will be archived: 3142869.
Resolved On: 11 Mar 2015 15:36:54 (UTC)
Ad Copy Uploaded

When a user uploads a new Ad Copy, you can opt in to being notified via the following email:

Subject New Ad Copy 8805830 uploaded
Body Id: 8805830
Name: wanted-tlr5_h720p
Created by User: chrisc
Created On: 12/30/08 8:10 PM
Size: 113 M, 730 K and 951 Bytes
Original File Name: wanted-tlr5_h720p.mov
Mime Type: mov
Ad Copy Approved

When a user approves an Ad Copy, you can opt in to being notified via the following email:

Subject Ad Copy 8805830 approved
Body Id: 8805830
Name: wanted-tlr5_h720p
Approved by User: chris
Approved On:Size: 113 M, 730 K and 951 Bytes
Original File Name: wanted-tlr5_h720p.mov
Mime Type: mov
Ad Copy Deactivated

When a user deactivates an Ad Copy, you can opt in to being notified via the following email:

Subject Ad Copy 8805823 deactivated
Body Id: 8805823
Name: mario_strikers
Deactivated by User: chris
Created On: 12/30/08 7:54 PM
Size: 56 M, 488 K and 548 Bytes
Original File Name: mario_strikers.avi
Mime Type: avi
New Campaign Created

When a new reservation or Campaign has been created, you can opt in to being notified via the following email:

Subject New Campaign 8805834 created
Body Id: 8805834
Name: Sharks Tale ~ C1
Created by User: chris
Created On: 12/30/08 8:16 PM
Start Date: 12/30/08 12:00 AM
End Date: 1/30/50 12:00 AM
Duration: 1 minute
Saturation: 1 Play per loop
Campaign Promoted

When a user promotes a Campaign from the Held state to the Contracted State, you can opt in to being notified via the following email:

Subject Campaign 8805834 promoted
Body Id: 8805834
Name: Sharks Tale ~ C1
Promoted by User: chris
Promoted On: 12/30/08 8:17 PM
Start Date: 12/30/08 12:00 AM
End Date: 1/30/50 12:00 AM
Duration: 1 minute
Saturation: 1 Play per loop
Campaign canceled

When a user cancels a Campaign, you can opt in to being notified via the following email:

Subject Campaign 1977214 canceled
Body Id: 1977214
Name: Trial 1 Campaign Music/Book 2
Canceled by User: chris
Created On: 7/27/15 5:47 PM
Start Date: 7/27/15 12:00 AM
End Date: 8/27/15 12:00 AM
Duration: 30 seconds
Saturation: 1 Play per loop
Ad Copies Added To Campaign

When a user adds Ad Copies to a Campaign, you can opt in to being notified via the following email:

Subject Ad Copies added to Campaign 8805843
Body Affected Campaign:
Id: 8805843
Name: Random Video ~ C1
Created by User: chris
Created On: 12/30/08 8:19 PM
Start Date: 12/30/08 12:00 AM
End Date: 1/30/50 12:00 AM
Duration: 2 minutes
Saturation: 1 Play per loop

Affected Ad Copies:
Id: 4353938Name: Least_Likely_PSA
Original File Name: Least_Likely_PSA.mpg
Size: 21 M and 522 K
Mime Type: mpg

Ad Copies Removed From Campaign

When a user removes Ad Copies from a Campaign, you can opt in to being notified via the following email:

Subject Ad Copies removed from Campaign 3141013
Body Affected Campaign:
Id: 3141013
Name: A Few good Vids
Created by User: chris
Created On: 3/10/08 3:10 PM
Start Date: 3/10/08 12:00 AM
End Date: 4/10/35 12:00 AM
Duration: 15 seconds
Saturation: 1 Play per loop

Affected Ad Copies:
Id: 4353936
Name: BlizzardRetrospectiveUS
Original File Name: BlizzardRetrospectiveUS.avi
Size: 43 M, 625 K and 392 Bytes
Mime Type: avi

Campaign Not ready

When a Campaign is created, you can opt in to being notified if any of the following is missing:

  • Active schedule
  • Active Bundle
  • Active Ad Copy
Subject Campaign “name_of_campaign” is not ready
Body Problem: No Media in Campaign
Campaign Id: 8805830
Campaign Name: name_of_campaign
Campaign Starts On: 12/30/08 at 09:00 AM
Campaign Ends On: 12/30/08 at 09:00 AM
Timezone: Eastern (-400 GMT)
Created by User: chrisc

Thresholds for this notification can be configured under the settings tab available in both campaign and customer folder properties. See Campaigns – Folder Properties, Contacts and Notifications and Customers – Folder Properties, Contacts and Notifications.

Backup Master Activated

When a Synchronization Set uses a backup master, and when a backup master rejoins a synchronization set as a slave, you can opt in to be notified via the following email:

Subject Incident 6044057 Resolved: Backup Master Activated
Body Id: 1929029
Name: player-win7
Type: Player
IP Address: 192.168.1.233
Private IP Address: 192.168.1.233
Domain: qaIncidentId: 6044057
Incident Type: Backup Master Activated
Problem Description: Player 1929029 took mastership, synchronisation set: abc.
Reported On: 21 May 2015 16:10:30 (UTC)
Resolved Description: Player 1929029 end of loop, synchronisation set: abc.
Resolved On: 21 May 2015 16:10:32 (UTC)

 

No Scheduled Campaigns

When a Display Unit contains a player that is without an active campaign during opening hours, you can opt in to be notified via the following email:

Subject Frame Fullscreen of DU1 has no scheduled campaigns
Body Warning: No Active Campaigns are scheduled on frame Fullscreen of DU1 after 2015-05-26Frame Id: 14807
Display Unit Id: 14805
Display Unit External Id: 12
Display Unit Name: DU1
Timezone: America/Montreal
Created by User: davidw
Players: 216 Win7 Android Imaging Box – 192.168.1.215

 

New Registration Added

When a user adds a new registration, you can opt in to being notified via the following email:

Subject New Registration Added 8805859
Body Registration Id: 8805859
Registration Name: Registration Activated
Primary MAC: ac:23:ac:23:ac:24
Secondary MAC: None
Registration Type: Player
Destination Folder Id: 1997376
Destination Display Unit Id: 8471426
Configuration Id: 1939045
Replacing Resource Id: 0
Requested From IP Address: 192.168.2.60
Registration Method: Wizard
Application Fault

When the Player encounters an application fault, you can opt in to being notified via the following email:

Subject Player 8492776 – Incident 15182030 Resolved: Application Fault
Body Id: 8492776
Name: TR – #27.95 – Windows Vista
Type: Player
IP Address: 192.168.27.95
Private IP Address: 192.168.27.95
Domain: hell
Incident Id: 15182030
Incident Type: Application Fault
Problem Description: This application encountered a problem and needed to be restarted.
Reported On: 30 Dec 2015 21:03:50 (UTC)
Resolved Description: The application was restarted.
Resolved On: 30 Dec 2015 21:03:42 (UTC)
Memory Exhausted

When a Player runs out of available memory and is forced to restart, you can opt in to being notified via the following email:

Subject Player 8492776 – Incident 15182029 Reported: Memory Exhausted
Body Id: 8492776
Name: TR – #27.95 – Windows Vista
Type: Player
IP Address: 192.168.27.95
Private IP Address: 192.168.27.95
Domain: hell
Incident Id: 15182029
Incident Type: Memory Exhausted
Problem Description: The computer was rebooted because memory usage thresholds were exceeded.
Reported On: 30 Dec 2015 21:03:50 (UTC)
Deadlock

When the Player freezes and needs to be restarted, you can opt in to being notified via the following email:

Subject Player 8492776 – Incident 15182032 Reported: Deadlock
Body Id: 8492776
Name: TR – #27.95 – Windows Vista
Type: Player
IP Address: 192.168.27.95
Private IP Address: 192.168.27.95
Domain: hell
Incident Id: 15182032
Incident Type: Deadlock
Problem Description: The application hung and needed to be restarted.
Reported On: 30 Dec 2015 21:11:39 (UTC)
Display – Temperature Critical

When an outdoor display’s temperature enters a range that you consider to be critical, you can opt in to being notified via email. The message will indicate a temperature state of “undefined”, “warning”, “critical”, or “back to normal”.

Subject Critical: Player demo-floor-player – Incident 349 Reported: Display – Temperature Critical
Body Id: 3022
Name: demo-floor-player
Type: Player
IP Address: 192.168.24.80
Private IP Address: 192.168.24.80
Domain: rootIncident Id: 349
Incident Type: Display – Temperature Critical
Problem Description: The device temperature is now in critical state.
Reported On: 6/26/15 8:09 PM (UTC)