# Graylog dashboard

**URL:** <https://community.graylog.org/t/graylog-dashboard/31547>\
**Category:** Graylog Central (peer support)\
**Tags:** dashboards\
**Created:** [February 18, 2024, 2:11pm UTC](https://community.graylog.org/t/graylog-dashboard/31547 "2024-02-18T14:11:10Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tammoy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tammoy/32/16342_2.png) [@Tammoy](https://community.graylog.org/u/Tammoy)\
**Post date:** [February 18, 2024, 2:11pm UTC](https://community.graylog.org/t/graylog-dashboard/31547/1 "2024-02-18T14:11:10Z")

</div>

Before you post: Your responses to these questions will help the community help you. Please complete this template if you’re asking a support question.  
**Don’t forget to select tags to help index your topic!**

**1. Describe your incident:**

need help to make dashboard

**2. Describe your environment:**

- OS Information:Graylog,Mikrotik,cisco,

- Package Version:

- Service logs, configurations, and environment variables:

**3. What steps have you already taken to try and solve the problem?**

**4. How can the community help?**

Can anyone suggest me how to do this type of dashboard.

 ![WhatsApp Image 2024-02-18 at 3.36.46 PM](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/b/4/b47d5309043981a7ca5162b3ae316f81d89cd4d4.jpeg)

**Helpful Posting Tips:** [Tips for Posting Questions that Get Answers](https://community.graylog.org/t/tips-for-posting-questions-that-get-answers/21828) [Hold down CTRL and link on link to open tips documents in a separate tab]

---

<div class="post-metadata">

**Author:** ![Joel\_Duffield](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@Joel\_Duffield](https://community.graylog.org/u/Joel_Duffield)\
**Post date:** [February 18, 2024, 5:09pm UTC](https://community.graylog.org/t/graylog-dashboard/31547/2 "2024-02-18T17:09:47Z")

</div>

Have you already parsed the messages into individual fields?

---

<div class="post-metadata">

**Author:** ![Tammoy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tammoy/32/16342_2.png) [@Tammoy](https://community.graylog.org/u/Tammoy)\
**Post date:** [February 18, 2024, 5:21pm UTC](https://community.graylog.org/t/graylog-dashboard/31547/3 "2024-02-18T17:21:44Z")

</div>

No, This pic is just a sample.

---

<div class="post-metadata">

**Author:** ![Joel\_Duffield](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@Joel\_Duffield](https://community.graylog.org/u/Joel_Duffield)\
**Post date:** [February 18, 2024, 7:34pm UTC](https://community.graylog.org/t/graylog-dashboard/31547/4 "2024-02-18T19:34:55Z")

</div>

So that’s going to be your first step, if you can post some examples of how the messages looks when they come in we can point you in the right direction. Once you have it parsed the rest is relatively easy.

---

<div class="post-metadata">

**Author:** ![Tammoy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tammoy/32/16342_2.png) [@Tammoy](https://community.graylog.org/u/Tammoy)\
**Post date:** [February 18, 2024, 8:07pm UTC](https://community.graylog.org/t/graylog-dashboard/31547/5 "2024-02-18T20:07:31Z")

</div>

firewall,info TCP\_: TCP\_ forward: in:TO\_DIST\_1\_BONDING out:vlan238\_INT, connection-mark:Padma connection-state:established,snat src-mac 18:fd:74:8c:7d:c8, proto TCP (ACK,FIN,PSH), 10.73.12.133:59476-\>31.13.64.18:443, NAT (10.73.12.133:59476-\>103.234.203.69:59476)-\>31.13.64.18:443, len 52

 ![Screenshot 2024-02-19 020611](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/d/5/d58083fb620715805b51191240449fbbdc14aa8d.png)

---

<div class="post-metadata">

**Author:** ![Joel\_Duffield](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@Joel\_Duffield](https://community.graylog.org/u/Joel_Duffield)\
**Post date:** [February 25, 2024, 4:13pm UTC](https://community.graylog.org/t/graylog-dashboard/31547/6 "2024-02-25T16:13:30Z")

</div>

Okay so GROK is probably the best option to parse that log. There are lots of posts about it, YouTube etc, it’s basically using regex to extract all the parts.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [March 10, 2024, 4:14pm UTC](https://community.graylog.org/t/graylog-dashboard/31547/7 "2024-03-10T16:14:06Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
