https://signoz.io
Join Slack
like a few other folks, I'm having trouble getting a nested json object (`body.message: {...}`) hois...
# support
a
like a few other folks, I'm having trouble getting a nested json object (
body.message: {...}
) hoisted to attributes. Over time, I might cherry-pick just a few of the attributes but even trying a few techniques (e.g. use JSON parser to temp variable from your JSON Guide) hasn't worked. I was hoping folks here might see the obvious mistake. Details in thread.
Here's the docker logs (shipped via logspout):
Copy code
bcs-web-test  | {"level":"info","message":{"error":null,"http-version":"1.1","method":"GET","referrer":"<http://localhost:3042/auth/sign-in>","remote-address":"::ffff:192.168.65.1","response-time":"5.337","status-code":"304","time":"2024-09-09T15:54:37.875Z","url":"/pricing","user-agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:129.0) Gecko/20100101 Firefox/129.0","user-email":null,"user-uuid":null,"x-forwarded-for":""},"service":"http","timestamp":"2024-09-09T15:54:37.875Z"}
here's what I see in SigNoz UI and rule I started with (deleted failed ones):
there are certain properties like 
status-code
, 
url
and such I'd like to have as direct attributes so it's easier to filter, group, alert, etc.
tia
as you can see, right now messages is created in attributes but as a string
n
You seem to have a nested json, as of now you will have to move them out manually to attributes using the 
move
operator. @Raj Kamal any easy way of doing this ?
a
Thx, I tried that and can try again but it never seemed to work. The pipeline wouldn't error out but the subsequent 
move
jobs after the initial json just silently failed. Is there way to debug? But I'll try again later today...maybe I was using 
add
or 
copy
instead of 
move
(would that make a difference?)
r
If you are looking to move only a few of the properties out of 
attributes.message
, 
move
operator should be the right choice. There is no easy way to hoist all nested properties up right now. However, a workaround would be to serialize the extracted 
attributes.message
map back to JSON and then use a JSON parser on it For example, you could use the 
add
processor to add the temp field 
attributes.serialized_message
with value 
EXPR(replace(toJSON(attributes.message), "\n", ""))
and then use a json parser on 
attributes.serialized_message
36 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by