Latest Contributions by GregoryChristakos

‎02-01-2024

Hi @MANESK - There's a few things you could try here: 1. If you can afford it, try pre-filtering the data so that you're only bringing in the data that matters, thereby shrinking the payload. 2. You could try increasing the polling interval to give GeoEvent Server more time to process the incoming records as events. 3. You could consider increasing the input buffer capacity. By default its 20MB but increasing it might prevent the overflow from happening for a time. This is a setting in GeoEvent Manager > site > settings. Check out this page. 4. It could be worth checking out how much RAM is available on the machine where GeoEvent Server is running and whether or not GeoEvent Server is having to compete with other processes that are also consuming RAM.

‎02-01-2024

Hi @Moi_Nccncc - I would recommend checking out this blog.

‎02-01-2024

Hi @Moi_Nccncc - This'll sound odd but you might want to flip this problem on its head. Rather than tracking the trucks, track the areas. If an area (the event) has a truck of type <A> inside of it, mark that area as "fully covered". If the same area (the event) has a truck of type <B> inside of it, mark that areas as "partly covered". The area (the event) can be, by default, not covered until it has a truck reported inside of it. Hope this helps!

‎02-01-2024

Hi @Nadia_Matsiuk - At a glance it looks like there's a certificate/trust problem here. When you access GeoEvent Manager on the machine where GeoEvent Server is installed, does the browser present you with certificate errors? If not, can the same be said when accessing GeoEvent Manager from another machine entirely? I often found that a failure to subscribe to a Stream Service is 9 out of 10 times due to SSL/trust and your errors seem to indicate this. This is likely going to require a deeper dive into your environment to resolve, and so I would definitely recommend reaching out to our Support Services for assistance, but just off the cuff here, here are some things I would look into if I were in your shoes: 1. Ensure you have the latest patch installed for 10.9.1. This would be patch 4. We did some work on stream services as a part of this cumulative patch. None of the issues are directly related to what you're reporting, but this is a good start nonetheless. 2. If you can hit GeoEvent Manager and are getting SSL/certificate errors in the browser, I would look into addressing this. If you have a domain certificate you can work with, that is by far more preferable than using a self signed certificate. I often tell folks that a self signed certificate is analogous to writing your name on a piece of paper and trying to get through airport security with it as a method of identification. Its really only good for you, or to bring this back to GeoEvent Server, its only good for doing anything on the machine/browser where GeoEvent is installed and running. Forcing the browser to "trust" the self signed certificate isn't guaranteed to work either unfortunately. - It'll be telling pretty quick if you can subscribe to the stream service from the browser where GeoEvent is installed/running, but cannot from anywhere else. 3. If you are using a domain level certificate, make sure you have the entire certificate chain imported into the ArcGIS Server admin endpoint. The root, any intermediates, and the cert itself. I've seen issues where just bringing in the cert alone isn't sufficient for establishing the chain of trust. 4. This might be a given, but did you try restarting GeoEvent Server following the certificate import you did on ArcGIS Server? Can you see if GeoEvent Server is presenting the new certificate when navigating to GeoEvent Manager? These are a few things I would look into checking myself, but as I said before it might be best to reach out to Support Services where an analyst can take each of these suggestions further as needed. Hope this helps.

‎02-01-2024

@Moi_Nccncc - There isn't a gallery of templated or example GeoEvent Services currently but this is something the Real-Time team can look into offering on the GeoEvent Server Gallery if there's enough interest from the broader community. I suggest posting this idea to our Ideas page if you haven't already! In the short term, I would recommend checking out some of the various recorded GeoEvent Server sessions from past conferences. Our "Applying Real-Time Analytics" line of sessions usually delve into GeoEvent Service design and demonstrations.

‎02-01-2024

@Moi_Nccncc - Incidents from the Incident Detector are managed in a separate cache/queue across all GeoEvent Services. The only way these incidents can be lost is by restarting the GeoEvent Server services (Windows services) or by restarting the machine where GeoEvent Server is running. Stopping and starting a GeoEvent Service, or republishing a GeoEvent Service isn't going to purge these incidents. Given this information, you should be able to update your GeoEvent Services per the normal pattern of use. In certain situations where an Incident isn't making logical sense anymore (e.g. an Incident is reported as ongoing from before the change, and you're trying to test/confirm that your latest changes are working and so the incident should be closed), it can be advantageous to restart GeoEvent Server too.

‎02-01-2024

Hi @Moi_Nccncc - You might want to look into using the Track Idle Detector Processor from the GeoEvent Server Gallery for this scenario. You can easily download and deploy it from the Gallery Add On Manager via GeoEvent Manager, or manually download and install it from here. Track Idle is designed to monitor whether an event has moved or not. You could use this event to then trigger an incident with the incident detector per your criteria (e.g. expire the incident after 5 mins, or close it if the track idle detector passes along an event indicating movement has occurred). You could apply the logic to your second scenario as well. If the incident is ongoing for more than 5 minutes, pass that along to a buffer processor and create a geofence via a sync rule. These geofences could then be used for the third scenario (i.e. monitor for ongoing incidents). What you're describing is within the realm of doable/possible and I think you're on the right track. All I would add here is that the Track Idle detector might make your life easier when monitoring for movement (or lack thereof).

‎01-31-2024

Hi @Mike_Quetel - A new version of the Waze Connector was released on Aug 25, 2023. You can download and deploy it directly from the Gallery Add-On Manager via your GeoEvent Manager interface (make sure the filter is set to samples and search for Waze), or you can manually download and deploy it from here.

‎01-23-2024

The development of a python processor to perform custom real-time geoprocessing or to trigger a python job elsewhere, is not on the GeoEvent Server road map at this time. Our team had initially done some exploration into this idea around the 10.8.1/10.9.0 timeframe but found that there were significant limitations with real-time data processing and workflows. As such, there are no plans to revisit this sort of enhancement as an out-of-the-box capability. Depending on the type of feature service you are working with, it could be worth exploring web hooks as an alternative mechanism for acting on adds, updates, or deletes to a feature layer being made by GeoEvent Server. In theory some feature services can be configured with a web hook to send a web request to an endpoint of your choosing whenever an add, update, or delete, is made to its feature layer. The endpoint can be what then executes a python script. In lieu of web hooks, it may also be possible to have GeoEvent Server construct a POST request to a similar sort of web endpoint that then triggers a python script asynchronously. Beyond that, we still recommend what @RJSunderman had mentioned before.

‎12-14-2023

The Introduction to GeoEvent Server tutorial series is being revamped. Available modules thus far can be found here: https://community.esri.com/t5/arcgis-geoevent-server-documents/introduction-to-arcgis-geoevent-server-tutorial/ta-p/1306781/jump-to/first-unread-message

‎12-14-2023

We support some of these authorization methods, but not all. It would be super if we could get some insight into which ones are the most important to folks to help prioritize enhancements moving forward. For more information on configuring a connector, see: https://enterprise.arcgis.com/en/geoevent/latest/reference/extend-using-out-of-the-box-components.htm Some of the out-of-the-box transports that can be used for a custom connector support auth methods like OAuth 1, basic auth, etc.

‎12-14-2023

If you're running GeoEvent Server 11.1+, you can deploy the Field Splitter Processor from GeoEvent Manager without the need to do anything with the GeoEvent SDK. See: https://enterprise.arcgis.com/en/geoevent/latest/reference/use-the-add-on-manager.htm#:~:text=To%20open%20the%20add%2Don,documentation%20for%20each%20add%2Don. Simply search for the Field Splitter Processor in the Gallery add on manager (within GeoEvent Manager) and deploy it via "install". Installed add-ons will persist on upgrade of GeoEvent Server. You can even obtain updated versions of this processor outside the normal release cycle using the add on manager (assuming there are updates available).

‎12-14-2023

‎12-14-2023

Implemented in 10.9.1 via the Field Mapper Processor. The Field Mapper Processor now supports in-line calculations on fields that you would otherwise have to define using the Field Calculator processor. Calculations can be performed on different fields all within a single Field Mapper Processor.

‎11-09-2023

What’s new in ArcGIS GeoEvent Server 11.2 ArcGIS GeoEvent Server 11.2 offers incremental improvements in usability and stability. We’re also excited to announce that several add-on connectors have been enhanced and are ready for use in GeoEvent Server 11.2 and prior. Let’s explore these changes in more detail. Create GeoEvent Definitions from Input Connectors First, GeoEvent Server 11.2 includes a new method for manually creating GeoEvent Definitions as a part of the configuration for an input connector. It is now possible to create and manually define a new GeoEvent Definition as part of an input connector without needing to navigate to a separate site settings page and lose any configured settings for the new input connector. Manually create a new GeoEvent Definition from an input connector using the new “Create new GeoEvent Definition” shortcut When an input connector is configured to have GeoEvent Server create its own GeoEvent Definition, GeoEvent Server interrogates the schema of inbound data to define its GeoEvent Definition; its blueprint for keeping track of the attribute fields and data types. While this hands-off approach is useful for quickly creating a definition that you can trust GeoEvent Server understands, it is important to note that a definition created this way is ephemeral. These types of definitions, commonly referred to as “managed GeoEvent Definitions”, are erased when GeoEvent Server is restarted. When this happens, what were once operational GeoEvent Services can enter an error state due to missing definitions on restart. It is a best practice to avoid using managed GeoEvent Definitions if you expect to stop GeoEvent Server or its underlying machine for any reason. A good way to tell if a GeoEvent Definition is managed is to check if the owner is “auto-generated” You can avoid using managed GeoEvent Definitions by creating your own GeoEvent Definition. This can be done one of two ways. The first method is to create a copy of a managed GeoEvent Definition so that its owner is your user account and is no longer ephemeral. The second method is to manually create your own GeoEvent Definition from scratch. While the latter approach has always been possible from the site settings page in GeoEvent Manager, GeoEvent Server 11.2 now provides the same interface for defining a GeoEvent Definition from scratch when configuring an input connector. Tracking GeoEvent Definition Usage We’re also excited to share that GeoEvent Server 11.2 now keeps track of which input and output connectors are using a GeoEvent Definition. This information is available when viewing a GeoEvent Definition from the site settings or service designer. With this change, you can now confirm how a GeoEvent Definition is being used before making any changes that could potentially break existing workflows. This example GeoEvent Definition is being used by two input and one output connector This improvement also extends to new warning messages that display when trying to delete a GeoEvent Definition that’s in use by an input or output connector. Avoid accidentally deleting important GeoEvent Definitions that are in use by your connectors. If a GeoEvent Definition is not being used by a connector, this new warning message will not display. A new warning prompts you to confirm deletion when a GeoEvent Definition is in use Gallery Add-On Updates With the introduction of the Gallery Add-On Manager in ArcGIS GeoEvent Server 11.1, we’ll be sharing updates made to various add-ons since the last release as a new practice moving forward. The following add-ons have been updated since GeoEvent Server 11.1 and can be installed automatically from the Gallery Add On Manager in GeoEvent Manager, or installed manually once downloaded from the ArcGIS GeoEvent Server Gallery. Unless otherwise noted, the new versions of these add-ons are compatible with GeoEvent Server 11.2 and earlier. Cityworks Connector for GeoEvent Server FlightAware Connector for GeoEvent Server Waze Connector for GeoEvent Server As always, please don't hesitate to visit What's New in GeoEvent Server 11.2 for more information!

Online Status	Offline
Date Last Visited	‎02-18-2026 01:55 PM

My Ideas

Latest Contributions by GregoryChristakos

Re: GEOEVENT "Buffer Overflow Channel" Error

Re: GeoFence spatial refernce

Re: Optimizing Truck Allocation for Area Coverage

Re: Stream Service - WebSocket issue

Re: Templete services and example

Re: Incident detector cached data and updating service

Re: Trucks sopped near to each others for period of time

Re: Waze Data Feed Updates

Re: Allow python scripting on GeoEvent Processor

Re: Update Introduction to GeoEvent Server for ArcGIS Pro

Re: Out-of-box support for external websites requiring authorization - Status changed to: Needs Clarification

Re: Add Field Splitter Processors as part of the standard installation - Status changed to: Already Offered

Re: Update Introduction to GeoEvent Server for ArcGIS Pro - Status changed to: Under Consideration

Re: GeoEvent Extension: Combine multiple Field Calculator processes into one - Status changed to: Implemented

What’s new in ArcGIS GeoEvent Server 11.2

Re: Geoevent Server Manger Access

Re: Waze Data Feed Updates

Re: GeoEvent: Polling from an External Website wit...

Re: Geoevent Connector For wireless protocols Thre...

Re: GeoEvent Field Name Inconsistencies