I’m new on Graylog usage and despite of reading documentation, I’m unable to know if Graylog can help me for my use case.
I wanted to analyse logs from my application in order to see if my items are well managed.
In applicative logs, these items are referenced by unique id and log lines gave information about my item lifecycle.
To make it simple, my logs look like that (I simplified the log lines):
Create CSV file with ItemId and Status, and assign new field Status based on ItemID using pipeline rule. Finally use this field in datatable in dashboard.
Thanks for this idea, that could be the good one.
I worked on it but I’m facing a Graylog limitation on updating CSV Lookup Tables using pipeline rules functions: https://docs.graylog.org/en/3.3/pages/pipelines/functions.html#lookup
So, I can’t update the status value in the lookup table.
I’m starting to try with MongoDB Lookup Tables, will see…
Why do you wan to update CSV lookup table using pipeline rule? Lookup table only read data from CSV file from disk and lookup for values in CSV based on key.
MongoDB lookup works only with enterprise license.
Sorry, I probably didn’t corectly understand your goal. CSV lookup table is read-only. I thought, that you wanted to only translate ItemID to status.
I didn’t play with mongo lookup, sorry.
you can modify those entries or create entries in the processing pipelines and a mongodb backend. you could even read/modify that via Graylog API from within any other application.
So you could decide to delete the entries when you have reached “completed” or you check all completed entries from outside and delete them after some time. This way you could verify later if those are completed or not.
I succeded to create a pipeline with rules to maintain a MongoDB lookup table that reflects the real time state of my items.
Now, I wanted to display this lookup table content by using a Graylog dashboard but I’m afraid that is not possible…
Could you confirm?
I also added a new field named “state” to my log messages but this state can only be considered as right if no new message with a same ItemId was received in the meanwhile (that’s why @shoothub suggested to me to use lookup tables)
Second question, does a “group by” feature exists on Graylog dashboards to be able to count only one time an ItemId with an “ONGOING” state?