Skip to Main Content
Ideas for RICOH ProcessDirector

Help us make RICOH ProcessDirector better for everyone!

Sign up to submit your ideas and to vote on the ones that we are considering right now.

After review and evaluation, your idea might show up on this list too. THANKS!

Please note that all ideas submitted become the property of Ricoh, LTD.

Status Under consideration
Created by Guest
Created on Sep 16, 2026

Guidance on which logs to send to Splunk, Elastic or Datadog and specific logs to trigger alerting on within them

We have RPD running on one server and have dynatrace installed collecting metrics and gaining some visibility into the API's and GUI processing. Like idea RPD-I-506 (Integration with OTel Standards for monitoring and alerting) we have a need to gain better visibility and have proactive alerting capabilities to the Ricoh platform. What we see is a very incomplete picture of what is happening under the covers.

Trying to search the logs is a frustrating experience as they are spread out over many folder locations and you can't correlate one request from one to the other across the logs.

We had a network problem recently where the login API was getting connection timeouts. It would retry and generally work on the 2nd or 3rd try, but dynatrace was unable to show the LDAP connection error that ended up in the /aiw/aiw1/trace folder. With RPD-I-506 dynatrace would have shown us the errors and retries. Without it we luckily found something in the System*Trace log a few days later that showed the LDAP connection error and the retries before they rolled off based on the log4j settings.

We would like to know what folder locations we should look for key logging information so we can ingest the data into a log tool so we can easily search all the logs and even create alerting based on certain ones.

What else besides these locations should we be looking?
/aiw/aiw1/trace/

/opt/infoprint/ippd/ws/logs/

/opt/infoprint/ippd/logs/

  • Attach files