Latest Contributions by RJSunderman

Hello @BarbaraS, My name is Dan and I work in Esri Technical Support. I would like to work with you through a support case on this behavior you describe here. I will direct message you to get additional information for creating the case. Kind regards, Dan

Hi @RJSunderman , thank you so much for the reply. However, I think I am still in need of some assistance here. Allow me to explain my issue further. My CSVs have multiple date and time fields. Some of them have Epoch Values which I was able to convert to desired MM/DD/YYYY MM:HH format, thanks to your earlier post. However, I also have some fields with 'Date' data type (not string) that have date values in them. Since my end users/client application require fields that have 'date' values only, I am trying to retain the original date only format. In the following screenshot, W is a 'date' field, X is a 'time' field and Y is a 'date' field with epoch values (the CSV was exported from SQL Server). I was able to convert X and Y respectively as 'string' and 'date' field (in geoevent definition). However, I want to import W column as date in feature service (with no time values). Is it possible in Geoevent/Portal? Or does Geoevent/feature service cannot handle date only fields? P.S - Following is a screenshot of a feature layer created using above CSV (different records, values do not correspond to CSV above). As you can see, 'call_created_date' field has unwanted and default 5 pm values appended to it. Thanks again for your time, Shital

If data you are receiving contains only a date value (e.g. 12/31/2021 ) without a time, this is not a pattern GeoEvent Server recognizes without you specifying a an Expected Date Format the inbound adapter can use to figure out how to parse a String as a Date. You would have to specify a value like MM/dd/yyyy when configuring your inbound connector. The connector will apply this pattern to all event record attributes whose data type is Date in the GeoEvent Definition used by the inbound connector. When I send the String value "12/31/2021" to my GeoEvent Server with the Expected Date Format configuration described above, the Date value my inbound adapter constructs for me from the received string is 1640937600000. This is an epoch value used by Java to represent date/time values. GeoEvent Server uses millisecond epoch values, which is why the value has 13 digits rather than only 10. If I ask GeoEvent Sever to cast its Date to a String I get a representation of the date which looks like "Fri Dec 31 00:00:00 PST 2021". Notice that the string has both a "date" and a "time" and includes the Time Zone for the expressed date/time value. In this case, the Date is expressed in the Pacific time zone. This is because an Expected Date Format pattern was specified -- which is required to handle the inbound string which does not match one of the few built-in expected patterns for a date/time value. The time zone handling is important to note because, in this case, the date/time is not in UTC units. GeoEvent Server assumes that the non-standard date/time must be a date/time local to my solution, so it uses the locale of my server (whose clock is configured to use the Pacific Time Zone). Focusing on your question, if you are receiving a string value which is somehow being adapted to produce the epoch date value 1640908800000 (which could also be represented as "Thursday, December 30, 2021 4:00:00 PM GMT-08:00" or "Thu Dec 30 16:00:00 PST 2021") and you need to truncate the value to be simply "Thursday, December 30" ... you have a couple of options. I strongly recommend you make sure you understand how the received data is actually being adapted, and check to verify how client applications are representing the value in web map pop-ups or web forms. A client application will likely represent a Java Epoch date/time value it receives, when querying a feature service for feature records for example, in whatever time zone the client web application is running. The value 1640908800000 already represents the date/time " Friday, December 31, 2021 12:00:00 AM " when a UTC value is assumed and web clients are likely going to try and represent an assumed UTC date/time in whatever time zone the web application is running. If you were to add or subtract some number of milliseconds from the epoch to drop the "time" portion and keep only the whole "date" value, your effort is likely going to have unintended consequences client-side. You could use a RegEx pattern match on a value toString(myDate) to isolate the whole hours portion of the "time" and then multiply this by 3,600,000 (which is 60 min x 60 sec x 1000 ms) and then subtract that from your Date using a Field Calculator. The eventual expression would be something like: myDate - (16 * 3600 * 1000) This assumes you are able to extract the value "16" from a string "Thu Dec 30 16:00:00 PST 2021" to know that you wanted to subtract 16 hours worth of milliseconds from the myDate attribute value. You also might want to look at some of the supported expressions for the Field Calculator processor. The function currentOffsetUTC() specifically computes the millisecond difference between your GeoEvent Server's locale and UTC. Since my server is configured to use the Pacific Time Zone, which is currently -08:00 hours behind UTC, the currentOffsetUTC() function returns a value -28800000, which is (8 hours x 60 minutes x 60 seconds x 1000 milliseconds). You might scale the computed value by some constant when performing date/time adjustment arithmetic, or more likely, shift an epoch Date from an assumed local time zone so that the value represents a UTC value. The advantage of using currentOffsetUTC() is that the function automatically recognizes changes in daylight savings, so you don't have to rely memory to update GeoEvent Services twice a year when a fixed constant value you might have hard-coded in an expression no longer reflects the observance of daylight savings time. See Also: What time is it? Well That Depends...

Thank you. That indeed helped. Instead of connecting field calculators along different paths, I stacked them one after another and that seems to have done the trick. Regards, Shital

Thank you, RJ! It's taken me awhile to get back to this, but did submit an incident into technical support. Being able to review the configuration of the stream service through the json is great! gives confidence for what is expected and can confirm that I didn't fat finger something in the set up. We've abandoned the idea of storing events at this point, just trying to get the related features to work as we have that scenario with a status being sent for a fixed asset - so would like to pull the location from the feature class. I'm optimistic we'll be able to get to the bottom of it and will report here for others that may run into similar -- jess

‎01-14-2021

Hi @GaryBowles1 , I was running into the same problem. I was able to get it to add the definitions after I published and ran the new GeoEvent Service. I stopped it quickly and then added the filter, but that was the only way I could get it to work. Thanks, Chris

‎12-04-2020

Very cool, Checking it out now. Thanks.

‎11-05-2020

In this blog we will take a deeper look at registering server connections with GeoEvent Server, something administrators commonly have to do to when configuring a GeoEvent Server deployment. Why do you have to register an ArcGIS Server connection with GeoEvent Server There are several different configurable components which require you to select a registered server and specify which services folder, map/feature service, and often a specific feature layer exposed by that service in order to use the feature layer's schema or feature records. A few examples include: The Poll an ArcGIS Server for Features input used to query a service for feature records. When you want to import a GeoEvent Definition from a feature service's schema . The Field Enricher (Feature Service) processor used to load a feature record set to use for enrichment. The Add a Feature and Update a Feature outputs used to persist data from processed event records as feature records in a geodatabase. All of the user-interfaces in the above examples populate their options from a cache of information GeoEvent Server collects when it queries a registered ArcGIS Server to discover published feature services. Service discovery is not performed the moment you click to open the panel. The cache is created and updated in the background because it can take several seconds – sometimes minutes or even tens of minutes – for GeoEvent Server to completely crawl the ArcGIS Server's REST Services Directory and query the information it needs from all of the available services. Which leads into the topic I want to address in this blog: Is there a way to know when service discovery is being run and how long it is expected to take? Using the ArcGIS Server Connection component to log messages You can configure the following component logger to request DEBUG messages be logged: com.esri.ges.datastore.agsconnection.DefaultArcGISServerConnection I've included a sample of the logged messages you will be looking for at the end of this article. Requesting this component logger include DEBUG messages in its logging will allow you to see, in the system log file, when the service discovery kicks off and which map/feature services it interrogates to learn about their layers. A message will be logged for every feature service being interrogated as well as a success message when service discovery is complete. There is no indication in the GeoEvent Manager web application that service discovery is about to start or is currently running. The best way to tell that service discovery is running is to start the workflow to import a GeoEvent Definition. If the blue/white indicator displays, requesting you "please wait", you know that the GeoEvent Server is busy updating its ArcGIS Services cache. Otherwise the GeoEvent Definition user-interface will display immediately allowing you to choose a server connection, folder, feature service, and feature layer. GeoEvent Manager does not allow you to configure, or schedule, when service discovery should take place. You are able to change the Discovery Rate for each server connection you register to specify how frequently a refresh should be performed. The default for recent software releases is every 60 minutes. I have personally found that when I use ArcGIS Pro, the Enterprise portal, or GeoEvent Manager to publish a new feature service, I want to use it now – so it is not uncommon for me to publish a feature service and immediately request GeoEvent Server run a service discovery to update its cache by clicking the refresh button on the server connection I have registered as a Data Store. This eliminates the need to have GeoEvent Server periodically refresh the cache for me, so I usually set the Discovery Rate for server connections I register to a fairly large value like 1440 minutes so that service discovery is run once once per day (or when GeoEvent Server is stopped and restarted). Service discovery takes too long and interferes with normal operations. Is there anything I can do? This is something the product team is working on. Refactoring GeoEvent Server to support all of the operations which use feature services, however, to interface with ArcGIS Server some other way is both high risk and high reward. Several different design options have been considered, but implementation has had to be deferred for each of the last several major releases. The best option for now, therefore, is to limit the number of features services which are discoverable each time service discovery is run. A recommended best practice is to configure your GeoEvent Server Data Store (e.g. the server connection you are registering with GeoEvent Server) with credentials. The user credentials do not have to be an administrative user, just a user who owns and published the feature service. You can use the Enterprise portal content item manager to assign existing feature services a new owner and configure GeoEvent Server to authenticate as that user when crawling the ArcGIS Server's REST Services Directory to limit the number of discoverable services. GeoEvent Server administrators often configure their registered server connections with the ArcGIS Server or Enterprise portal primary administrative account – which naturally sees all published services. If you can identify the feature services to which you want GeoEvent Server to write data, or from which you want GeoEvent Server to retrieve feature records or a feature layer's schema, and assign ownership of just those services to a user set aside specifically for your "real-time" data, you can improve service discovery considerably by not crawling all of the feature services being maintained by more traditional feature editing workflows. The trick is to identify the feature services your GeoEvent Server components actually care about and limit discovery to only those feature services. Example messages logged by the ArcGIS Server Connection component logger 2020 - 11 - 05T13 : 55 : 02 , 124 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | sleep interrupted java . lang . InterruptedException : sleep interrupted at java . lang . Thread . sleep ( Native Method ) ~ [ ? : ? ] at com . esri . ges . datastore . agsconnection . DefaultArcGISServerConnection$CacheUpdater . run ( DefaultArcGISServerConnection . java : 235 ) [ 56 : com . esri . ges . framework . datastore . agsconnection - datastore : 10.8 . 1 ] 2020 - 11 - 05T13 : 55 : 02 , 124 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Exiting Cache Updater run method . . . . 2020 - 11 - 05T13 : 55 : 03 , 274 | DEBUG | qtp808353329 - 598 | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Create an instance of CacheUpdater . . . . 2020 - 11 - 05T13 : 55 : 03 , 274 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating cache for DataStore Public_Esri_Hosted_Server . . . 2020 - 11 - 05T13 : 55 : 08 , 944 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "Active_Hurricanes_Sampler" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 15 , 296 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "Active_Hurricanes_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 21 , 613 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "Air_Quality_PM25_Latest_Results" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 23 , 311 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "ASAM_events_V1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 25 , 033 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "Coral_Reef_Stations" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 27 , 876 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "GDELT_Health_Pandemic" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 29 , 170 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "GDELT_v1_Social_Tones" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 30 , 368 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "IHME_Projected_Peaks_QA" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 31 , 995 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "Median_Sea_Ice_Extent_for_the_Antarctic" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 32 , 995 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "Median_Sea_Ice_Extent_for_the_Arctic" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 34 , 063 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "MODIS_Thermal_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 35 , 225 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "National_Farmers_Market_Directory" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 36 , 445 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "ncov_cases" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 38 , 421 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NDFD_Ice_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 40 , 579 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NDFD_Precipitation_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 43 , 479 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NDFD_SnowFall_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 45 , 920 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NDFD_WindForecast_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 49 , 935 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NDFD_WindGust_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 51 , 519 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NDFD_WindSpeed_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 53 , 124 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NDGD_SmokeForecast_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 54 , 193 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NOAA_METAR_current_wind_speed_direction_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 55 , 683 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NOAA_short_term_warnings_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 55 : 58 , 401 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NOAA_storm_reports_Sampler" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 00 , 844 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NOAA_storm_reports_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 06 , 494 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NWS_Watches_Warnings_Sampler" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 12 , 942 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "NWS_Watches_Warnings_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 19 , 622 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "Recent_Hurricanes_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 21 , 726 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "Satellite_VIIRS_Thermal_Hotspots_and_Fire_Activity" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 22 , 871 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "seaice_extent_N_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 23 , 976 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "seaice_extent_S_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 25 , 081 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "SPI_recent" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 28 , 250 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "Standardized_Precipitation_Index_(SPI)" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 31 , 492 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "US_Cases_per_county_(time)" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 33 , 073 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "USA_Wildfires_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 35 , 074 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating layers for Service ( Folder : "/" , Name : "USGS_Seismic_Data_v1" , Type : "FeatureServer" ) . 2020 - 11 - 05T13 : 56 : 36 , 595 | DEBUG | Public_Esri_Hosted_Server - Updater | DefaultArcGISServerConnection | 56 - com . esri . ges . framework . datastore . agsconnection - datastore - 10.8 . 1 | Updating cache for DataStore Public_Esri_Hosted_Server done . Success : true . ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ You can see from the above that discovery of 36 feature services hosted by an external, public server, took just over 90 seconds. The more services there are to discover, the longer service discovery will take. See Also: GeoEvent Server > Administer > Data stores in the GeoEvent Server on-line help Debug Techniques - Configuring the application logger GeoEvent Server blog series GeoEvent Configuration: Data Store Connections w/Tokens blog by Eric Ironside

‎07-10-2020

Questions and Answers from the Expo Floor: What is ArcGIS GeoEvent Server GeoEvent Sever is one of several license roles for ArcGIS Enterprise. You license and install GeoEvent Server to add real-time capabilities to your Enterprise. GeoEvent Server, out-of-the-box, provides configurable inputs for connecting to a variety of data streams from virtually any data provider. What is a GeoEvent Service A GeoEvent Service is an event processing workflow you design and publish using the GeoEvent Manager web application. You drag, drop, and configure an input to specify how data will be received. You add and configure an output to specify what will be done with the data the GeoEvent Service processes. You then add one or more filters and processors to the service, connect the nodes to define an event processing workflow, and publish the GeoEvent Service. See Also: GeoEvent Server inputs GeoEvent Server filters GeoEvent Server processors GeoEvent Server outputs What's New in GeoEvent Server 10.8 / 10.8.1 Significant work went into simplifying common user workflows enabling users to maintain their focus on configuring and publishing GeoEvent Services. Most of what you need to do is now done from within the Service Designer rather than switching to a different web page in the GeoEvent Manager. The status, catalog, and option to create, edit, and delete primary service components (inputs, outputs, etc.) is now available from a consolidated Monitor page in the GeoEvent Manager. There is also a new GeoEvent Sampler utility built into the Service Designer allowing you to see the effect filters and processors you configure have on event records as they are received in real-time. For details, please see the PDF attached to this article. Question Answer Question Answer Question Answer

‎04-20-2020

Similar to Eric's idea, I would be interested in a geoevent processor that could trigger a python script. So, if a certain condition is met a python script would be called. This would provide a lot of flexibility for those who are not familiar with java it also opens up a new ability to extend the GE functionality as a whole i.e. using python geoprocessing tools, reporting, access to custom python geoprocessing tasks etc.

Online Status	Offline
Date Last Visited	3 hours ago

My Ideas

Latest Contributions by RJSunderman

Re: HowTo: Administratively Reset GeoEvent Server (10.5.x / 10.6.x)

Re: Default Timestamp Automatically Gets Added To The Date Field

Re: Converting between Date Formats

Re: Geoevent Erroneously Imports Date Field

Re: Stream Service - Store latest, review configuration

Re: Geoevent Filter to ensure a date field is within a tolerance of the current time

Re: Ais decoder

Monitoring a registered web server's service discovery

UC 2020 FAQ

Re: Allow python scripting on GeoEvent Processor

ArcGIS Analyse