Great to hear. Since I’m pretty new to ES & Kibana… I was hoping to identify some role models to spark ideas and help affirm my approach.
So… given that the most common ElasticSearch use case is to index NOSQL “documents” for the sake of providing search & insights in the context of an application… I’m wondering whether you are essentially indexing structured “documents” from your robots via Log Message + extra fields?
I know that log message will add a string into the log, and since I haven’t used the extra fields yet, I don’t know what kind of additional structure that introduces into the log message. I’m guessing the normal Log Message item is already JSON format behind the scenes. Do you have a sample of what that format looks like? I don’t have access to our ES instance yet to see it.
When we add new fields, are they just sibling elements next to the original log message field (within the same object), or are they child elements of the main log message element? I’ll be trying it myself soon… but if you had a quick sample of what a message with extra fields will look like, it would help me wrap my brain around it.
I’m trying to imagine whether I have any ability to create a hierarchical relationship (nested objects) using “add log fields”, or if I would need to create my own JSON objects in the standard “log message” call to accomplish that.
Before I learned about extra fields I was imagining that I might create my own JSON string (having multiple NVP) that describes a searchable entity… and then simply logging that.