Hello,
I'm working with Peoplesoft, Elasticsearch and Kibana. I have a native query that generates accounting entry information. When executed, all the information is shown correctly, including the drill-down URL. If I run tests to see how it will be exported to Elasticsearch, the resulting file also displays correctly including the drill-down URL. However, when it's transferred to Elastic, the drill-down URL is modified, changing the server and portal name to generic data. Does anyone know what needs to be configured within Peoplesoft so that Elasticsearch receives the correct information?
Hello @Leonardo_Soto_T
Welcome to the community!!
The URL formed is on the source (Peoplesoft) which is correct & while sending this to Elasticsearch, server/portal name are replaced with generic information. Is this understanding correct?
If yes, could you please share as to how the data is sent from Peoplesoft to Elasticsearch?
If logstash/ingest pipeline is used in your current usecase?
Thanks!!
Hi:
Yes the url is formed on Peoplesoft, and it is sent through integration broker to logstash, somehow during this step url is modified.
I believe that it is peoplesoft the one changing it but when we check the query or the Search definition preview we get the correct url.
Example:
What we see at Query level and in Search Definition data preview:
http:/ /150.53.112.105:31270/psc/fs92dev_newwin/EMPLOYEE/ERP/c/PROCESS_JOURNALS.JOURNAL_ENTRY_IE.GBL?Action=U&BUSINESS_UNIT=XXXXX&JOURNAL_ID=0000638&JOURNAL_DATE=2024-06-15&UNPOST_SEQ=0
Vs what arrives to Elastic:
http:// myserver/psc/ps_newwin/EMPLOYEE/ERP/c/PROCESS_JOURNALS.JOURNAL_ENTRY_IE.GBL?Action=U&BUSINESS_UNIT=XXXXX&JOURNAL_ID=0000638&JOURNAL_DATE=2024-06-15&UNPOST_SEQ=0
The url on Peoplesoft side is assembled dynamically so I think we are missing one configuration.
I was wondering if someone had this same issue at some point.