Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Technical Training Serssions 2021 Linux Team
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Session Harsh for Team about Infosys-ITD ELK Deployment . Dated 26th Mar 2021 == {{#ev:youtube|e7AfaibdCVM|640}} '''Video summary:''' [PARTIAL TRANSCRIPT QUALITY - heavily garbled Hindi ASR with technical terms frequently mis-transcribed; summary reflects only confidently identifiable content] "ELK Training By Harsh" -- an internal training session on the ELK (Elasticsearch, Logstash, Kibana) stack plus Kafka, using the Income Tax Department of India as a real client example of the architecture. Explains the general log-pipeline pattern: Filebeat-type lightweight shipper agents run on each source device/server to pick up and forward logs; Kafka sits in between as a message broker/buffer so many source devices' logs can be collected without overwhelming the pipeline; Logstash parses and transforms the incoming log data; and Elasticsearch indexes and stores it for fast search. Kibana then provides the graphical dashboard/visualization and search layer on top, including building different reports/visualizations per log type when there are many source servers to monitor. Frames the use cases in relatable terms: comparing it to how large platforms (Facebook, Google) use similar log/event-analytics platforms to detect and moderate problematic content at scale, and describing security/infrastructure use cases like traffic monitoring, alerting, and correlating activity across many devices in an organization's environment. Given the heavy transcription noise throughout, exact configuration steps and commands could not be reliably captured -- this summary reflects only the architecture and concepts that came through clearly.
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)