jkharrat

5 ms·

1.
Practical – Embedding Confluence data into ChromaDB through Gitlab pipelines(medium.com)
1 points by jkharrat 3y ago|0 comments
2.
by jkharrat 4y ago
Notes from the author: This story is not a push for a standard but rather an attempt to create a logically organized log format optimized for log parsing systems like newRelic or ELK etc. It will help you generate useful dashboards, metrics
3.
by jkharrat 4y ago
I agree with the simplicity approach I like it too. However, I think sometimes we do not have a choice especially in distributed sytems or "micro"services environement. I think with great "complexity" comes great respons
4.
by jkharrat 4y ago
This is an attempt to create a logically organized log format optimized for log parsing systems like newRelic or ELK etc. It will help you generate useful dashboards, metrics and event notifications (example: trigger an alert if the percent
5.
by jkharrat 4y ago
Sometimes you face an edge case that cannot be reproduced easily even while waiting for this enhanced logs level. I would 1/ still log as much as possible, 2/ implement a smaller logs rotation period (upload logs to glacier or S3
6.
by jkharrat 4y ago
I would do the same if I was you. I will still have a log whenever we catch an error because it will help debugging this cron or job or even identify an issue in the provided data. No matter how divisive the opinions about logging are, I st
7.
by jkharrat 4y ago
Der @thamer thanks for the advice. I have added it to the article :) Much appreciated