LogEntry doesn't appear to be logging correctly

Ask the community
1

I am reading the SPI docs for logging/LogEntry.

https://www.wix.com/velo/reference/spis/site-monitoring/logentry/operation

The operation > producer key is of interest to me, but I don’t think it’s working according to the docs.

If I understand correctly, I should be able to simply console.log(“blah”) from either page code, or a .jsw, and the LogEntry should reflect some useful information in the operation > producer field.

The docs state:
producer - string - Context of the operation, such as a URL path for page code or a web module function name.

and the examples they give are:
Page Code:

"operation": {
     "id": "1554017373.14484058793726342",
     "producer": "page:/about", // URL path of page within site
   },

.jsw:

   "operation": {
     "id": "1554017373.14484058793726342",
     "producer": "httpFunction:myFunction",
   },

However, this is not what is showing up in my site monitoring (using either the built in Site Events, or Stackdriver)

Here is what my operations > producer looks like:

Page Code:

"operation":{
"id":"..........EtUPiIyLSCbAv6OxK6aoBn"
"producer":"https://polkaset.wixsite.com/testing"
}

For page code, the producer is the same as the siteUrl, which is logged here:

"labels":{
"siteUrl":"https://polkaset.wixsite.com/testing"

.jsw

"operation":{
"id":"1659816281.667625528788316967"
"producer":"backend"
}

FWIW, I tried this on both a premium site, and a basic site. Both had the same (incorrect?) behavior.

Thanks in advance
Tracey

2

Hi there,
The team is investigating this issue. I’ll let you know as soon as I hear back from them.

3

The team is still investigating and will likely contact you for more information. Thanks for your patience!

4

@marlowe-shaeffer Do you mind keeping us posted on the outcome :slight_smile:

5

This looks like mistakes in our documentation.
The location in the code which triggered the error should be in sourceLocation, not in operation.producer.

697×618 52 KB

Are you not getting those values in the logs?

6

@danielor I’ve check what you said about the information being available in sourceLocation. Unfortunatly frontend logs do not have sourceLocation property.

hence, there is no way to know where the log occurred for frontend logs.

Is this something you’ll be fixing? If so, can we expect a fix soon?