Monday, December 16, 2024

ELK(Elastic Search) Engineer--McLean,VA(Onsite)

Role: ELK(Elastic Search)  Engineer
Location: McLean,VA(Onsite)

Job Description

• Design and implement ELK (Elastic Search, Logstash and Kibana) solutions.

• Hand-on Experience in creating and managing index's in Elasticsearch based on requirements.

• Hands-on experience in writing JSON queries to select/insert/update/delete data in Elasticsearch.

• You have extensive experience in at least one of the pillars of observability: Logs, Metrics, APM, Synthetic Monitoring or Prof

• Designing and implementing solutions for centralized logs, infrastructure and health metrics, distributed tracing for different

• Hands-on experience on both on-prem and cloud instances

• Fine tune bulk load process.

• Provide Elastic Search tuning/optimizing based on application needs.

• Create and troubleshooting Dashboard on KPIs.

• Contribute to team design discussions with detailed technical information.

• Develop code with quality, scalability, and extensibility.

• Provide work breakdown and estimates for new requirements.

• Identify strategic/tactical solutions and provide risk assessments and recommendations.

• Influencing other teams and engineering groups in adopting logging best practices.

• Troubleshooting problems, inyolving the appropriate resources and driving resolution of issues with a focus on minimizing imp Applying best practices for managing cluster, scaling and capacity planning.

• Excellent verbal and written communication skills, a great teammate with strong analytical, problem solving, debugging



--
You received this message because you are subscribed to the Google Groups "c2cactiverequirements2023Bharath3" group.
To unsubscribe from this group and stop receiving emails from it, send an email to c2cactiverequirements2023bharath3+unsubscribe@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/c2cactiverequirements2023bharath3/CANoWkO_qcLNMftuw%2B%2BNzci%3DaorYej24eZmdj676ROHU43w%3Df6w%40mail.gmail.com.

No comments:

Post a Comment