Viewing the service logs (on-prem)

Logs for all Netcool Agile Service Manager services can be found in the $ASM_HOME/logs/<service> directories. You can set logging levels for the user-facing services, such as the observers and inventory (previously 'search'), using scripts provided.

About this task

You can change your current log levels to the following values (INFO is the default log level):

OFF
ERROR
WARN
INFO
DEBUG
TRACE
ALL

Log housekeeping

When a log reaches its maximum size, it is compressed, date-stamped and versioned, and moved to a subdirectory, for example:

$ASM_HOME/logs/topology/tmp/topology-service-2017-03-23-0.log.gz

and then


$ASM_HOME/logs/topology/tmp/topology-service-2017-03-23-1.log.gz

Tip:

Event integration on-prem: To avoid excessive disk usage with event integration enabled on an on-prem system, change the LOG_LEVEL for the topology and status services to WARN.

Network Discover Service logs:

Network Discovery logs: All log files start with 'nasm-net-disco'.; Discovery worker logs have one previous version stored and are rotated when the size of the file exceeds 10Mb.; Other Network Discovery log files are stored for five days and rotated when the size exceeds 10Mb, or when the total size of all log files exceeds 20Gb.

Table 1. Log names and directories for Netcool Agile Service Manager services
Service	Directory	Log
Application Discovery service	$ASM_HOME/logs/app-disco	pss (primary storage server) ds (discovery server) sss (secondary storage server)
Cassandra database	$ASM_HOME/logs/cassandra	system.log
Elasticsearch	$ASM_HOME/logs/elasticsearch	elasticsearch.log
Gateway service	$ASM_HOME/logs	gateway.log
Kafka message bus	$ASM_HOME/logs/kafka	server.log
Network Discovery service	$ASM_HOME/logs/net-disco	Log files start with 'nasm-net-disco'
Observer service	$ASM_HOME/logs/observer
Probe service	$ASM_HOME/logs/probe	asm_probe.log
Inventory service	$ASM_HOME/logs/inventory	inventory-service.log
Status service	$ASM_HOME/logs/status	status-service.log
Topology service	$ASM_HOME/logs/topology	topology-service.log
UI API service (see the UI API service logging example)	$ASM_HOME/logs/ui-api	ui-api.log
Zookeeper synchronization service	$ASM_HOME/logs/zookeeper	zookeeper.log

UI API service logging example: The UI API logging script follows the same rules as all other logging scripts.
The Agile Service Manager UI uses the UI API to retrieve data from the other Agile Service Manager services. Data retrieval errors are recorded in the UI API log.
Use the following shell script to change your logging level:

/opt/ibm/netcool/asm/bin/ui_api_log_level.sh

The INFO setting outputs AUDIT log messages, which means that CRUD operations (that is, CREATE, READ, UPDATE and DELETE operations) will be logged. To diagnose more specific problems, a lower log level may be useful, such as DEBUG or TRACE, which logs all incoming requests as well as an indication of success. At a setting of ALL, additional details are logged about how each REST request is handled. When setting the log level, you may want to consider disk usage. The ALL log levels uses the most space.