GOES DCS FIELD TEST
ENTER THE 8-CHARACTER DCP ADDRESS ASSIGNED TO THE PLATFORM USED BY THE FIELD TEST WHEN QUERYING FOR MESSAGES.
THE START AND END DATES SPECIFY A RANGE OF TIME USED BY THE FIELD TEST WHEN QUERYING FOR FOR MESSAGES FROM THE PLATFORM.
CLICK THE START OR END DATE TEXTBOX AND SELECT THE DESIRED DATE FROM THE DATEPICKER CALANDER. THE ENTIRE 30-DAY SET OF
DCS MESSAGE DATA RETAINED BY DADDS MAY BE QUERIED.
DETERMINES LOOK-BACK PERIOD IN HOURS USED WHEN QUERYING FOR MESSAGES FROM THE CURRENT DAY, AND IS ONLY USED WHEN THE START
AND END DATES SET TO THE CURRENT DAY. THE DEFAULT FIELD TEST QUERY SEARCHES HAS A LOOK-BACK PERIOD OF 1 HOUR TO QUERY FOR
FOR MESSAGES RECEIVED IN THE PREVIOUS HOUR.
USE OF THE FIELD TEST NOW REQUIRES A VALID DCS WEBSITE ACCOUNT. IF YOU DO NOT HAVE AN ACCOUNT YOU MUST REGISTER TO CONTINUE
USING THE DCS FIELD TEST. REFER TO THE NOTICE AT THE TOP OF THE PAGE FOR INFORMATION ON OBTAINING AN ACCOUNT.
Notice to Users
As of November 1st, 2021 use of the DCS Field Test requires an active DCS website account. Users who do not have
an account must register for continued access to this page. Accounts for users who are not affiliated
with an active DCS Group will be restricted to field test use only. To request a field test account simply double click anywhere
within the notice area and complete the DCS account registration form.
A recent update of the DCS website included changes to the DCS Field Test to restrict its usage to users with a DCS website
account. Access to the field test now requires login credentials be submitted along with query parameters, and will authenticate
a user before executing a field test query. Because of this, requests from
automated systems began to fail, and continued to do-so until the necessary changes were made to the automated scriots. While
some systems handled the failures in an acceptable manner, others responded by increasing the frequency of the field test query
requests which lead to denial of service conditions and website outages. When failed requests are handled correctly, automated
systems can continue request attempts and not cause denial of service driven outages. The field test and automation
help document contains
examples, potential pitfalls and best practices to help users create robust automated systems.