Implementation > UD Agents

UD Agents

Discovery

UD Agent Install: UD Agent package available for most of the operating system flavors. It is extremely important to understand the options you have with the agent installer before you package them via software distribution systems or automation tools.

Discovery

Discovery Job – Call Home Processing

Call Home provides a way for discovery nodes to communicate with the Data Flow Probe. Based on your enterprise size, network latency and the frequency of changes to the CI environments, you need to set the appropriate call home setting on the agent. Once it is set, the agent tries to send a call home to the probe IP configured, which creates a Call Home Event CI on a server.

This trigger is then processed by the call home processing job. You can also look at the global setting to tweak the right time interval to fit your enterprise needs.

Global Setting:

Discovery

Server Cloning with UD Agents

With increasing dependencies in cloud and virtualization, cloning a server with a server image is very common in the industry. If UD agents are installed on your image, make sure you create a new UD Unique ID from the commands below from the post install scripts.

ud_unique_id is used as a critical differentiator in identification and validation rules. The chances of merging two servers with the same UD Agent ID becomes higher.

Windows:  discagnt.exe --newuniqueid

UNIX:  discagnt --newuniqueid

Discovery

Leverage Scope, UD Certificates

Create a discovery account for agentless discovery. Having a single account helps to simplify discovery job execution.

If you add multiple entries, you can use scope to limit the credential scope to a specific network segment.

Job Timeouts will have a direct impact when you have multiple credentials for network scope (ALL).

If you deployed UD agent in workstation and server environments, and if you want to discover them in two separate instances, you can use different UD certificates to distinguish these environments.

Discovery