ELK deployment instructions #332

Closed
opened 2022-03-29 16:23:18 +00:00 by hbelakon · 9 comments
hbelakon commented 2022-03-29 16:23:18 +00:00 (Migrated from gitlab.com)
No description provided.
hbelakon commented 2022-03-29 16:23:18 +00:00 (Migrated from gitlab.com)

assigned to @sivayavvari

assigned to @sivayavvari
sivayavvari commented 2022-03-29 16:51:10 +00:00 (Migrated from gitlab.com)

Shared the ELK setup instructions along with the credentials needed as part of them setup.

Shared the source repo for the installation and the reference links for the installation of the filebeats on the server.

Also sharing the here:

The ELK deployment is done by following the documentation on the git repo: https://github.com/deviantony/docker-elk
If the containers keep crashing then consider changing the jvm heap memory https://github.com/deviantony/docker-elk/blob/main/docker-compose.yml#L39. As of now the running elk has 12gb confugured.

File beat installation:
https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-installation-configuration.html
After downloading the filebeat, the filebeat.yml file needs to be modified , config file on irona server at /etc/filebeat/filebeat.yml can be used as reference.

Everything from ELK side is working fine. If any server/appplication logs need to be sent to ELK, then filebeat should be installed on the server and the logs file path should be included in the inputs section of the filebeat.yml file.
For different type of inputs refer to: https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-options.html

Shared the ELK setup instructions along with the credentials needed as part of them setup. Shared the source repo for the installation and the reference links for the installation of the filebeats on the server. Also sharing the here: The ELK deployment is done by following the documentation on the git repo: https://github.com/deviantony/docker-elk If the containers keep crashing then consider changing the jvm heap memory https://github.com/deviantony/docker-elk/blob/main/docker-compose.yml#L39. As of now the running elk has 12gb confugured. File beat installation: https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-installation-configuration.html After downloading the filebeat, the filebeat.yml file needs to be modified , config file on irona server at /etc/filebeat/filebeat.yml can be used as reference. Everything from ELK side is working fine. If any server/appplication logs need to be sent to ELK, then filebeat should be installed on the server and the logs file path should be included in the inputs section of the filebeat.yml file. For different type of inputs refer to: https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-options.html
sivayavvari commented 2022-03-29 16:51:56 +00:00 (Migrated from gitlab.com)

Assigning it to @rilesdun for review.

Assigning it to @rilesdun for review.
sivayavvari commented 2022-03-29 16:52:11 +00:00 (Migrated from gitlab.com)

assigned to @rilesdun and unassigned @sivayavvari

assigned to @rilesdun and unassigned @sivayavvari
rilesdun commented 2022-03-30 14:49:00 +00:00 (Migrated from gitlab.com)

assigned to @sivayavvari

assigned to @sivayavvari
rilesdun commented 2022-03-30 14:49:10 +00:00 (Migrated from gitlab.com)

unassigned @rilesdun

unassigned @rilesdun
sivayavvari commented 2022-03-31 02:11:01 +00:00 (Migrated from gitlab.com)

AttachingELK_docker_deployment_guide.docx the deployment instructions document

Attaching[ELK_docker_deployment_guide.docx](/uploads/5c663dc5c793c94ee2a6ef81b4f2bf70/ELK_docker_deployment_guide.docx) the deployment instructions document
sivayavvari commented 2022-03-31 14:31:13 +00:00 (Migrated from gitlab.com)

@rilesdun Please review the document uploaded and let me know if you have any questions

@rilesdun Please review the document uploaded and let me know if you have any questions
sivayavvari commented 2022-03-31 14:31:32 +00:00 (Migrated from gitlab.com)

assigned to @rilesdun

assigned to @rilesdun
rilesdun (Migrated from gitlab.com) closed this issue 2022-04-01 16:39:43 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Peerplays_Blockchain/peerplays_migrated#332
No description provided.