16.00 - Self-Registration - Teradata Ecosystem Manager

Teradata Ecosystem Manager Installation, Configuration, and Upgrade Guide for Customers

Teradata Ecosystem Manager
December 2016

Self-registration enables automatic recognition of newly monitored entities. Ecosystem Manager creates new metadata when receiving events that identify new entities. Ecosystem Manager creates the metadata for new data centers, servers, daemons, daemon groups, tables, applications and jobs and sets up dependency relationships between them. This reduces the amount of manual configuration you need to do in the Ecosystem Configuration portlet.

For self-registration to work, enable the self-registration setting for the global parameters in the Ecosystem Configuration portlet.

The following table shows self-registration cases for various entities:

New Entity Detected Event Flag Cases
Data center -e flag in the sendevent command  
Teradata System

(Pre-classified as a Teradata component and registered under the data center specified in the event. If the data center is not specified, the data center is listed as UNKNOWN. )

--tds flag in sendevent command
  • Target server (TDPID) as specified in job events (START, STEP, END)
  • Unity-managed TDPIDs(UNITYSTATE event)
  • HCHK events from TD servers using EMDCS service
Server HCHK metric events with --tds flag set to 'COMPONENTS' HCHK events from client server using emmonitor service.
Daemon HCHK metric events for a daemon using TDPID flag set to 'DAEMONCOMPONENTS' HCHK events from client server using emmonitor service.
Job -r and -t flags in the sendevent command line START/STEP/END events with new Job ID (-r or --jid) comes in for the Teradata system specified in the event (--tds flag)
Application --app flag specified
  • -app flag should be filled in
  • Start/STEP/END Events must have non-empty Database Name/Table Name with a valid TDPID