Work-at-Sleek

Desc: My job requires working with Camunda to develop workflows for automation and implementation. FEEL is the language that is used mainly in Camunda. Below are some resource that help you quickly adapt this language: Docs: https://docs.camunda.io/docs/components/modeler/feel/language-guide/feel-expressions-introduction/ Playground: https://camunda.github.io/feel-scala/docs/playground/ This post is imported from: https://thebrownbox.hashnode.dev/how-to-learn-feel-in-camunda

Desc: Basic setting for memory and CPU in container How basic knowledge is very important Measurement Unit The most important thing is that we have to know the unit of each one: CPU: is measure by CPU unit Memory: Mebibyte, Gibibyte,… How to setting them With CPU: It’s a float: cpu: "0.5" or cpu: "1" "0.5" can represent like "500m" With Memory: Mebibyte: Mi Gibibyte: Gi apiVersion: v1 kind: Pod metadata: name: example-pod spec: containers: - name: example-container image: example-image resources: requests: memory: "512Mi" # Memory request cpu: "250m" # CPU request (0....

Logs should be long enough to have all the needed information and short enough not to cause any effect on the system (large log files, etc.). They should also be in a good format for easy traceability and alertness. Below is my current strategy for log and alerting. My current project use Splunk for logs, it supports alert to Slack! How I log NOTE: If you want to log the output/result of a function, log it inside the function, so you don’t have to duplicate that log, also you don’t forgot to add it outside whenever the function is called/used....