Configure Settings for Error Logs

Need to troubleshoot errors? As an administrator, you can change logging levels and download logs for Oracle Integration.

Use caution when changing logging levels because increasing them can affect performance. Reset logging levels back to default settings after troubleshooting.
  1. From the Home page, select Settings, then Logging.
    The Logging screen is displayed. By default, loggers are contained within folder containers, and the number of loggers contained (collapsed) within the folder is listed after the folder name.
  2. Filter and sort the logging list.
    You can filter in several ways:
    • Show Only: Select one or more options to limit the list. Note that loggers or folders must meet all selected options to be listed.
      • Oracle Integration Cloud: Displays loggers related to Oracle Integration components.

      • Top Containers: Displays the two top levels of folder containers.

      • Unsaved Changes: Displays loggers whose levels you have changed but haven’t saved, as indicated by an Unsaved Unsaved icon.

    • Filters Menu: Select Open Filters Menu Open Filters menu to view loggers by their status (at default, or increased or decreased) or by their selected logging level. Filter settings display below the search field as you specify search criteria.
  3. Search for logs.
    In the Search field, enter a logger name (or partial name) and press Enter. Searching is case sensitive. For example, enter oracle.bpm to list all loggers that begin with those characters. Note that searching is performed within the filtered list. For example, if the Top Containers filter is selected, only the top containers are searched.
  4. Change logging levels as needed.
    • Use the up and down icons in the Logging Level column to change a logger level. As you increase or decrease, an unsaved icon displays adjacent to the new logging level to indicate unsaved changes. The Status column indicates whether you increased or decreased the level and lists the default level.
    • When a logging level lists Inherited, this indicates that its own current level is inherited from its parent package because it doesn’t have a default level set. Children packages may have a different level. Changing a package level will automatically change the logging level of its children if they inherit from it (if they don’t have a specific logging level set).
    • To return to previous settings, click Revert and revert to either the last saved configuration or set all levels back to their default level.
  5. Save your changes. Download logs as needed.
    Click Download Logs and save the entire logging file to a zip file.