Sign In   Register
  Friday, 24 August 2018
  3 Replies
  192 Visits
0
Votes
Undo
  Subscribe

Can the System Event Publisher be used in place of logging to the TM Database? i.e. in busy environments would it be possible to configure it so that debug logging went exclusively to Splunk or AWS without ever creating a record in the TM database? 

2 months ago
·
#14253
0
Votes
Undo
For more information on System Event Publisher, please see https://docs.avoka.com/SystemEventPublisher/SystemEventPublisherOverview.htm
Sergey Eremenko revoked the reply #14252 as the answer for this post — 2 months ago
Chris Eagar selected the reply #14252 as the answer for this post — 2 months ago
2 months ago
·
#14248
0
Votes
Undo
Hello,

This is an old thread but we had the same requirement and the same approach was recommended by our Temenos support person. We tried this but still groovy logs are not getting pushed to server.log file on our Linux platform. We updated the standalone.xml (single node environment) and restarted the JM instance.
<logger category="com.avoka.core.groovy.GroovyLogger">
<level name="ERROR"/>
</logger>

Is there anything else we are missing here?

Thank you,
Kalpesh
0
Votes
Undo

Hi Bryce,

I presume you are referring to Groovy Service Log Data in this questions, e.g. DEBUG and INFO messages recorded using the logger in Groovy Services.

The GroovyLogger class internally has a SLF/Log4J logger which logs messages to the TM service.log file. The Log4J level for this service is configured in the standalone.xml configuration file.  The default logging level is ERROR, which means DEBUG, INFO and WARN messages are not logged to disk.  The reason for this default setting is to prevent PII data being logged to disk.

<logger category="com.avoka.core.groovy.GroovyLogger">
<level name="ERROR"/>
</logger>

If this is configured to INFO or DEBUG level then GroovyLogger statements at those levels will be logged to the server.log file.  From here they can be feed into Splunk or other log management systems, regardless of the TM Groovy Service Logging configurations for the database.

With regard to the System Event Publisher can feed Groovy Service Log Data message to an AWS SQS endpoint to support integration with other log management systems without having to write PII data to disk.  The Groovy Service Log Data messages will include the same content as would be included in the TM Groovy Service Log Data records, so it cannot be used as a complete substitute to the TM Groovy Service Log records.

regards Malcolm

  • Page :
  • 1
There are no replies made for this post yet.
Be one of the first to reply to this post!

Q&A Forum - Tips

The purpose of the Temenos Journey Manager platform (TJM) Q&A forum is for all clients and partners to seek help...

Read More

Not a member?

Register to ask a question and access to more content.

Join now

Looking for something else?

You can request access to:

  • Courses
  • Full Release Notes
  • Product Downloads
  • SDK

Request access

Leader Board

1
Mark Murray
User's Points: 1360
2
Lin Vanoevelen
User's Points: 1046
3
Julio Berrueco Pinto
User's Points: 715
4
Matthew White
User's Points: 386
5
Chad Thomas
User's Points: 300