Monitor application execution logs

​

Execution logs

​

Application logs

​

Support bundle

​

View your front-end logs

1. List your all namespaces to find the name of your platform namespace:
   kubectl get namespace
   
2. List all the pods in your platform namespace to find the name of a front-end. You likely have more than one frontend pod.
   kubectl get pods  -n <namespace for your platform nodes>
   
3. Print the front-end logs for one of your frontends.
   kubectl logs <pod name of your frontend pod> -n <namespace for your platform nodes> -c nucleus-frontend
   

• Platform namespace This namespace hosts the core application components of the Domino application, including API servers, databases, and web interfaces. The installer configuration file defines the name of this namespace at namespaces.platform.name. The following components running in this namespace produce the most important logs:

  Component	Logs
  nucleus-frontend	The nucleus-frontend pods host the frontend API server that routes all requests to the Domino application. Its logs contain details about HTTP requests to Domino from the application or another API client. If you see errors in Domino with HTTP error codes like 500, 504, or 401, you can find corresponding logs here.
  nucleus-dispatcher	The nucleus-dispatcher pod hosts the Domino scheduling and brokering service that sends user execution pods to Kubernetes for deployment. Errors in communication between Domino and Kubernetes result in corresponding logs from this service.
  keycloak	The keycloak pod hosts the Domino authentication service. The logs for this service contain a record of authentication events, including additional details on any errors.
  cluster-autoscaler	This pod hosts the open source Kubernetes cluster autoscaler, which controls and manages autoscaling resources. The logs for this service contain records of scaling events, both scaling up new nodes in response to demand and scaling down idle resources, including additional details on any errors.

• Compute grid namespace This namespace hosts user executions plus Domino environment builds. The installer configuration file defines the name of this namespace at namespaces.compute.name. Logs in this namespace correspond to ephemeral pods hosting user work. Each pod contains a user-defined environment container, whose logs are execution logs. There are additional supporting containers in the pods, and their logs might contain additional information about errors or behavior seen in specific Domino executions. Domino advises that you aggregate and keep at least 30 days of logs to facilitate debugging. You can harvest these with a variety of Kubernetes log aggregation utilities, including:
  • Loggly
  • Splunk
  • New Relic

​

Next steps

• Project audit logs for project-level auditing including user permissions and Dataset-related actions.
• The Audit trail data glossary contains Domino audit event names along with their descriptions.
• Data Source audit logs create an audit trail for Data Source activity and records the WHO, WHERE, WHEN & WHAT for user activity.