psadmin.conf: System Performance Data Collection

In this session from psadmin.conf 2018, Frank Dolezal shares how he collects logs and system analytics to address a number of system issues. He explains how they can track average performance trends in the system, identify errors an anomalies, catch new issues before they are reported, and more.

We released the videos from psadmin.conf as a free course so you can find the sessions in one place. Head over to the courses page and sign up. If you already signed up for the course, you can log in and the new video will be available.

PeopleSoft Instrumented Development Diagnostic Aid (IDDA)

I stumbled across this page about the PeopleSoft IDDA logger in PeopleBooks today. I haven’t seen this tool before, so I wanted to give it a quick test to see how it works. I wanted to know what type of data the IDDA logged and if the data would be useful for troubleshooting issues. After setting it up in a Development environment, I found that the PIA, Portal and Authentication traces would be helpful for sign on or cookie issues.

Enabling IDDA

You enabled the IDDA in a Web Profile Custom Property and by changing the IDDA log settings in on your web server.

Web Profile

Go to your active Profile and add this custom value:

  • Property Name: IDDA
  • Validation Type: Number
  • Property Value: The bit value, or sum of bit values, for the area you want to trace.

If you want to trace the PIA and Report Repository, enter a value of 5.

Bit Value Functional Category
1 PeopleSoft Internet Architecture
2 Integration Broker
4 Report repository
8 Portal
16 Web server caching
32 File processing (attachments)
64 Authentication
128 Performance Monitor
256 Web Services for Remote Portlets (WSRP)
512 Jolt

Save the Web Profile changes.

Logging Properties

Open the file under webserv\domain\piaconfig\properties and change the .LEVEL value. These are the possibles values:

  • OFF: Disables all IDDA logging.
  • SEVERE: Displays server issues, such as premature termination and failure.
  • WARNING: Displays less severe issues, such as configuration issues.
  • INFO: Displays basic operational information, such as starting and stopping.
  • FINE, FINER, FINEST: Displays internal non-critical informational messages.
  • ALL: Enables all logging levels. The default value is INFO.

I tried ALL, FINEST and INFO during my testing. I ended up sticking with FINER since I felt that gave the best detail without too much information.

PeopleBooks has the wrong path documented if you look there. You can find the location of the file by opening setEnv.cmd and looking at the PSLOGGING variable path. Save the changes and reboot your web server.

Viewing IDDA Data

IDDA output will write to webserv\domain\servers\PIA\logs\PIA_servlets.%u.log. The output is plain text so you view it in any text editor. The output is also tab-delimited, so importing the log files into Excel or another log view is easy.