GEODI can use high CPU and memory at maximum speed. You have a few options:

1. Depending on the processed types, this may be temporary; after a while CPU/memory usage may drop.

2. You can reduce the speed; after a while CPU and memory needs will decrease, but the discovery time will increase.

3. There may be other applications using the same server.

4. You can increase your machine’s CPU and/or memory capacity.

GEODI keeps logs under appdata/dece/geodi. These logs are in CEF format and can be processed by SIEM tools.

For a SIEM connection, the logs are located in the directory %AppData%\Dece\Logs\GEODI\AppUsage.

It is also possible to use the syslog protocol.

For query tracking, when you mention a colleague in notes, an email is sent. There may be an issue with the server settings set up for this purpose. You can access them via the GEODI Administration Panel/settings.

If the problem occurs for only a limited number of users, check Spam folders or mail rules.

At startup, GEODI checks whether an update is available and, if you approve, it may be installed. Depending on the features in the new version, the index structure may be converted to the latest version. This is indicated with a warning. Before proceeding, it is recommended to back up the old index. GEODI must be closed while the update is being performed.

Absolutely. Endpoint discovery or classification operations can cause access or performance issues. Agents not seeing the GEODI Server, policies not being updated, slowness in classification, slowness in discovery with the GDE Discovery agent, and many other problems may occur.

Required exceptions must be defined for GEODI DSPM and the agents.

Power outages, hardware problems, or the deliberate closing of the application may cause the index to be incomplete/incorrect. Index repair fixes these errors as much as possible.

However, backing up and resuming from backup is always the safest and healthiest way. Default project templates always have automatic backup enabled. You have likely disabled backups. We recommend waiting for the repair to finish before allowing backup.

GEODI is designed to optimize server use. Server memory and CPU resources are used dynamically. The number of concurrent tasks increases for simple/fast files and is reduced for heavy files.

1. If processing is progressing too slowly, increase the speed; set an indexing speed value between 1 and 5. As speed increases, the number of concurrent processes as well as CPU and memory needs also increase.

2. Memory may be low or being used by other processes running on the server.

3. There may be CPU-intensive operations such as heavy OCR.

4. Network connections to the file server may be very slow.

5. There may be a lot of logs, CSVs, and large Excel files.

6. There may be network issues with the database connection or excessive load/pressure on the database.

In such cases, only the file name is indexed and marked with [!]. Encrypted files can be queried with “status:GEODICryptedContent” or “status:GEODICryptedContentPart”; faulty files can be queried with “status:HasScanError”.

For agent-based discoveries carried out with GDE, this is the expected situation. To remove files deleted at the sources from the GEODI index, you need to perform the “delete deleted items” operation from the Project Management interface.

Windows can access directories up to 260 characters in length. After this value, the error “System.io Path too Long Exception“ is received; as a solution you can adjust the path appropriately (mapping).

Please follow the checklists on the GDE page. If installation details are correct, a firewall, DLP, or similar tool on the network may be blocking access.

Agent updates are performed automatically via the GEODI Server.

For details, please refer to the GDE or Classification pages.