Overview of AtomSphere Logs for Troubleshooting

Document created by Adam Arrowsmith Employee on Oct 21, 2015Last modified by Adam Arrowsmith Employee on Mar 15, 2017
Version 9Show Document
  • View in full screen mode

Below is a list of the AtomSphere logs for troubleshooting.

 

LogLocationDescription
Test Mode (Process and Document Logs)
AtomSphere Test Mode UI:
  • Process – Click Process Name at top > View Log.
  • Document – Select step on canvas, then view Logs tab at bottom.

Created automatically by the Atom and available after the execution completes.

  • Process – Primary means of investigation execution problems. Log of given execution including the steps executed, number of documents per step, step execution duration, and step at which exception occurred. Can be augmented with user-defined entries by using the Notify shape or custom scripting.
    •  Save larger logs locally to view more easily.
  • Document – Additional document-level information such as parameter values and individual step evaluations (info varies by step type).
Process  Reporting (Process and Document Logs)
AtomSphere UI: Manage > Process Reporting
  • Process – Click Log icon for execution record.

  • Document – Click execution timestamp > select Start step > select View Logs from gear picklist.

Created automatically by the Atom and available after the execution completes.

  • Process – Primary means of investigation execution problems. Log of given execution including the steps executed, number of documents per step, step execution duration, and step at which exception occurred. Can be augmented with user-defined entries by using the Notify shape or custom scripting.
    •  Save larger logs locally to view more easily.
  • Document – Additional document-level information such as parameter values and individual step evaluations (info varies by step type).
Atom Container LogAtomSphere UI: Manage > Atom Management > select Atom > Log Files > Atom Logs

Locally: ../<atom_install_dir>/logs/yyyy_MM_dd.container.log

Created automatically by the Atom.

  • Used for general runtime health and errors that typically occur outside the context of a single process execution, such web server and other listener issues or problems communicating with the AtomSphere platform. Contains uncaught exceptions so can be an additional source to check for problems if nothing shown in process execution.
  • Running daily log per node of runtime activity. Does not include history of all executions. SEVERE entries are of most interest.
  • Purged according to Atom’s purge schedule (30 days by default).
  • See Understanding the Container Log.
Shared HTTP Server Log

AtomSphere UI: Manage > Atom Management > select Atom > Log Files > Shared Server Logs

 

AtomSphere UI: Dashboards > HTTP Status Dashboard

Locally: ../<atom_install_dir>/logs/ yyyy_MM_dd.shared_http_server.log

  • Used to help troubleshoot incoming requests that do not result in an execution from the platform’s perspective.
  • Running daily log of inbound web service requests per node. Info includes timestamp, target endpoint, user, HTTP status, and response time.
  • UI dashboard contains summary info only.
  • Purged according to Atom’s purge schedule (30 days by default).
  • See Understanding the HTTP Shared Server Log.
Molecule Node ViewsAtomSphere UI: Manage > Atom Management > select Molecule > Cluster Status

Locally: ../<atom_install_dir>/bin/views
  • Series of files indicating Molecule cluster health such as is there only one head node, do all the nodes know about one another, are all the nodes responsive. UI displays status graphically.
  • Typically monitored by operations group.
Install4j LogLocally, ../<OS temp dir>/install4jError<generated number>.log
  • Used to troubleshoot failed installations of new runtimes.
AS2 Artifacts

AtomSphere UI: Manage > Atom Management > select Atom > Log Files > AS2 Artifacts

 

Locally: ../<atom_install_dir>/work/as2
MDNRequestLog files

  • Used to help troubleshoot AS2 issues. The MDN Request Logs contain more detailed information and errors for EDI related problems.
MLLP ArtifactsAtomSphere UI: Manage > Atom Management > select Atom > Log Files > MLLP Artifacts
  • Used to help troubleshoot MLLP issues.
Heap Dump (hs_pid_err.log)Locally: ../<atom_install_dir>
  • When advised by Dell Boomi support, used to assist with diagnosing memory-related issues. The Atom runs on a Java runtime environment (JRE). If the Java runtime experiences a catastrophic failure or exception and crashes the atom, this “dump” file may get created. Used to analyze the stack dump for which method was being called when the failure occurred. Typically issues with drivers or added jars outside of the Atom code could cause this to occur. See High-volume troubleshooting for more information.
User Log (for processes)Locally only: ../<atom_install_dir>/logs/<Process_Name>.yyyy_MM_dd.log
  • This per-process log is only available for local runtimes and is only accessible via the file system (not the UI) and therefore is not often used.
  • Entries are created using the Notify shape with the "Enable User Log" option enabled. The log only contains entries explicitly created by you.
  • Entries are written immediately and available mid-execution, not at the completion of the process. This can be helpful to track progress for long running executions such as migrations or initial loads.
  • Test Mode executions write to the log.
  • Running daily log per process.
  • Purged according to Atom’s purge schedule (30 days by default).
7 people found this helpful

Attachments

    Outcomes