SY Showing posts older than #2562 · Back to latest
Forwarded from Timur Tukaev
Forwarded from Коробочка хорони
Forwarded from Технологический Болт Генона
[lua] Failed to run module rulesets callback late_routing: /usr/local/nginx-fl/lua/modules/init.lua:314: attempt to index field 'execute' (a nil value)
if rule_result.action == "execute" then
rule_result.execute.results = ruleset_results[tonumber(rule_result.execute.results_index)]
end
Forwarded from /usr/bin
Forwarded from Будни сетевика
Forwarded from DevOps
git revert и git reset. Но они работают по-разному!soft, mixed, hard.revert — безопасный и прозрачный способ отменить изменения. reset — мощный инструмент, но требует осторожности.Forwarded from Человек и машина
Forwarded from Мониторим ИТ
Forwarded from Алексей Рыбак: системный дизайн, хайлоад, разработка с агентами
Forwarded from Безумный кот
Forwarded from Технологический Болт Генона
FlowExporter is a sidecar that runs alongside all Netflix workloads in the AWS Cloud. It uses eBPF and TCP tracepoints to monitor TCP socket state changes. When a TCP socket closes, FlowExporter generates a flow log record that includes the IP addresses, ports, timestamps, and additional socket statistics. On average, 5 million records are produced per second.
. . .
FlowCollector, a backend service, collects flow logs from FlowExporter instances across the fleet, attributes the IP addresses, and sends these attributed flows to Netflix’s Data Mesh for subsequent stream and batch processing.
. . .
As noted in our previous blog post, our initial attribution approach relied on Sonar, an internal IP address tracking service that emits an event whenever an IP address in Netflix’s AWS VPCs is assigned or unassigned to a workload.
. . .
Attributing local IP addresses for container workloads running on Netflix’s container platform, Titus, is more challenging. FlowExporter runs at the container host level, where each host manages multiple container workloads with different identities. When FlowExporter’s eBPF programs receive a socket event from TCP tracepoints in the kernel, the socket may have been created by one of the container workloads or by the host itself. Therefore, FlowExporter must determine which workload to attribute the socket’s local IP address to. To solve this problem, we leveraged IPMan, Netflix’s container IP address assignment service.
Forwarded from Записки админа
Forwarded from Виталий
Forwarded from DevOps&SRE Library
A deployment orchestration tool that simplifies multi-cloud, multi-region, and multi-service deployments.
Forwarded from DevOps&SRE Library