corentinaltepe
commented
1 year ago Hi @240026763 I'm not sure I want to implement such feature into the library because it goes against Loki's best practices : Static labels are good, Use dynamic labels sparingly
Are you sure you want to go this way?
It is generally much better to parse your loki logs into json to get the property you want to obtain as a label. Below an example loki query, where you filter logs by two Static labels, and one nlog property that is part of the json payload of the log content.
{label1="a", label2="b"}
| json
| property1="c" Would that work for you?
240026763
I use properties in my log events which I want to put into Loki as Metadata (labels) but not every log event uses every property and I'd rather not have to statically define each property in the config. Can we add an option in the target to convert all the properties of the nlog event into Loki labels (perhaps could parse out
${all-event-properties:separator=|}? I use scoped, event, and global properties. I'm fine with the global properties being added into the target config manually since they are static once set (also makes a much more standardized way of pulling in things like app name without statically putting it in the file like${gdc:item=AppName}