Name Service: Operations

This statistic shows requests made to the name service.

An understanding of operating system internals is helpful to interpret this statistic.

When to Check Name Service Operations

Use the hit/miss breakdown to check the effectiveness of the NSCD cache. Misses become backend requests to remote sources, which can be examined by using the type of operation breakdown of the name service lookups statistic. See Name Service: Lookups.

Name service analytics should be used primarily to analyze performance and diagnose name service problems during investigations. Name service analytics should not be run continuously because they will unnecessarily consume system resources. You can generate an alert if the average latency substantially increases for a period of time, and the alert will appear on the dashboard. To set a threshold alert, see Configuring a Threshold Alert - BUI, CLI.

Name Service Operations Breakdowns

Table 6-26 Breakdowns of NSCD Operations

Breakdown	Description
type of operation	Request type.
result	Success or fail.
database name	Name service database, such as LDAP, DNS, or NIS.
latency	Time for this request to complete.
hit/miss	Result from the cache lookup.

Further Analysis

For average latency, see Name Service: Operations Average Latency. To examine lookups instead of operations, see Name Service: Lookups.