Elastic search (ELK) stack configured
- or -
Post a project like this2649
$$
- Posted:
- Proposals: 0
- Remote
- #1405391
- Awarded
Description
Experience Level: Intermediate
General information for the business: Service Provider
Description of requirements/functionality: We have built and ELK stack which is running, but requires configuration. The server is dedicated for capturing syslog from network devices.
Requirements
- Syslog from two different network device types (Cisco and Huawei). Logstash, beats or another method is required to identify the syslog fields so they can be later searched such as syslog severity. At present syslog is still going to rsyslog where it is currently forwarded to ELK, but this can be changed/removed as required.
- Once logs are present it would be great to have a few basic Kibana dashboards to make some sense of the syslog information for example;
- Number of logs from each host
- Highest recurring messages
- Number of messages by syslog severity
Restrictions: Network devices sending the syslog must use tcp or udp port 514 as the destination port. Again happy for rsyslog to be removed from this server or listening on port 514 disabled etc.
Specific technologies required: Linux, ELK
OS requirements: Linux
Extra notes:
Platform: Cent OS 7.3
ElasticSearch 5.1
Logstash 5.1
Kibana 5.1
Description of requirements/functionality: We have built and ELK stack which is running, but requires configuration. The server is dedicated for capturing syslog from network devices.
Requirements
- Syslog from two different network device types (Cisco and Huawei). Logstash, beats or another method is required to identify the syslog fields so they can be later searched such as syslog severity. At present syslog is still going to rsyslog where it is currently forwarded to ELK, but this can be changed/removed as required.
- Once logs are present it would be great to have a few basic Kibana dashboards to make some sense of the syslog information for example;
- Number of logs from each host
- Highest recurring messages
- Number of messages by syslog severity
Restrictions: Network devices sending the syslog must use tcp or udp port 514 as the destination port. Again happy for rsyslog to be removed from this server or listening on port 514 disabled etc.
Specific technologies required: Linux, ELK
OS requirements: Linux
Extra notes:
Platform: Cent OS 7.3
ElasticSearch 5.1
Logstash 5.1
Kibana 5.1
Dan K.
100% (1)Projects Completed
1
Freelancers worked with
1
Projects awarded
67%
Last project
25 Jan 2017
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies