How to make one discover table link to another discover table in Dashboard or elsewhere?
up vote
0
down vote
favorite
I'm using elasticsearch + kibana + logstash + filebeat
latest 6.4.1 to collect and analyze web logs. The columns of my log are like:
timestamp, http_method, request_uri, http_status, host, user_agent, client_ip, client_port
I have configured ELK to show my logs in Kibana. But now I want to see my logs in sessions. I hope the log lines can be grouped by session and shown in Kibana's Discover
page. In my scenario, the log lines with the same (host, client_ip)
belong to the same session.
I hope to have this:
Session table
name, client_ip, host
session1, www.google.com, 1.2.3.4
session2, www.bing.com, 5.6.7.8
session3, www.google.com, 4.3.2.1
When I click one of the above session (e.g., session1), I can see all the records of that session in the following 2nd table:
Log table
timestamp, http_method, request_uri, http_status, host, user_agent, client_ip, client_port
20181105, 21:33:17.773, POST, /index.html, 200, www.google.com, chrome 59, 1.2.3.4, 1234
20181105, 21:33:18.773, POST, /abc.html, 200, www.google.com, chrome 59, 1.2.3.4, 1234
20181105, 21:33:19.773, POST, /index.html, 404, www.google.com, chrome 59, 1.2.3.4, 5678
I know Elasticsearch does flat indexing, it's not easy to have hierarchy between documents. I'm OK to create separated indices for the above two tables. I know Dashboard can show two Discover tables at the same time. But my question is:
How to link these two tables? When I click one item in the Session table, the Log table will show corresponding contents?
Or is there any other way to fulfill my requirement (view session-based logs easily in Kibana)? Thanks.
UPDATE
The index for Log table contains the session field, which can be session1
, session2
, etc. Both indices are under my control. So I can add any field if needed.
elasticsearch kibana kibana-6
add a comment |
up vote
0
down vote
favorite
I'm using elasticsearch + kibana + logstash + filebeat
latest 6.4.1 to collect and analyze web logs. The columns of my log are like:
timestamp, http_method, request_uri, http_status, host, user_agent, client_ip, client_port
I have configured ELK to show my logs in Kibana. But now I want to see my logs in sessions. I hope the log lines can be grouped by session and shown in Kibana's Discover
page. In my scenario, the log lines with the same (host, client_ip)
belong to the same session.
I hope to have this:
Session table
name, client_ip, host
session1, www.google.com, 1.2.3.4
session2, www.bing.com, 5.6.7.8
session3, www.google.com, 4.3.2.1
When I click one of the above session (e.g., session1), I can see all the records of that session in the following 2nd table:
Log table
timestamp, http_method, request_uri, http_status, host, user_agent, client_ip, client_port
20181105, 21:33:17.773, POST, /index.html, 200, www.google.com, chrome 59, 1.2.3.4, 1234
20181105, 21:33:18.773, POST, /abc.html, 200, www.google.com, chrome 59, 1.2.3.4, 1234
20181105, 21:33:19.773, POST, /index.html, 404, www.google.com, chrome 59, 1.2.3.4, 5678
I know Elasticsearch does flat indexing, it's not easy to have hierarchy between documents. I'm OK to create separated indices for the above two tables. I know Dashboard can show two Discover tables at the same time. But my question is:
How to link these two tables? When I click one item in the Session table, the Log table will show corresponding contents?
Or is there any other way to fulfill my requirement (view session-based logs easily in Kibana)? Thanks.
UPDATE
The index for Log table contains the session field, which can be session1
, session2
, etc. Both indices are under my control. So I can add any field if needed.
elasticsearch kibana kibana-6
Does the log table/index also have a field containing the session name, i.e.session1
?
– Val
Nov 8 at 4:48
@Val yes, the index is under my control. I can add any field if needed.
– Yang Luo
Nov 8 at 4:53
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using elasticsearch + kibana + logstash + filebeat
latest 6.4.1 to collect and analyze web logs. The columns of my log are like:
timestamp, http_method, request_uri, http_status, host, user_agent, client_ip, client_port
I have configured ELK to show my logs in Kibana. But now I want to see my logs in sessions. I hope the log lines can be grouped by session and shown in Kibana's Discover
page. In my scenario, the log lines with the same (host, client_ip)
belong to the same session.
I hope to have this:
Session table
name, client_ip, host
session1, www.google.com, 1.2.3.4
session2, www.bing.com, 5.6.7.8
session3, www.google.com, 4.3.2.1
When I click one of the above session (e.g., session1), I can see all the records of that session in the following 2nd table:
Log table
timestamp, http_method, request_uri, http_status, host, user_agent, client_ip, client_port
20181105, 21:33:17.773, POST, /index.html, 200, www.google.com, chrome 59, 1.2.3.4, 1234
20181105, 21:33:18.773, POST, /abc.html, 200, www.google.com, chrome 59, 1.2.3.4, 1234
20181105, 21:33:19.773, POST, /index.html, 404, www.google.com, chrome 59, 1.2.3.4, 5678
I know Elasticsearch does flat indexing, it's not easy to have hierarchy between documents. I'm OK to create separated indices for the above two tables. I know Dashboard can show two Discover tables at the same time. But my question is:
How to link these two tables? When I click one item in the Session table, the Log table will show corresponding contents?
Or is there any other way to fulfill my requirement (view session-based logs easily in Kibana)? Thanks.
UPDATE
The index for Log table contains the session field, which can be session1
, session2
, etc. Both indices are under my control. So I can add any field if needed.
elasticsearch kibana kibana-6
I'm using elasticsearch + kibana + logstash + filebeat
latest 6.4.1 to collect and analyze web logs. The columns of my log are like:
timestamp, http_method, request_uri, http_status, host, user_agent, client_ip, client_port
I have configured ELK to show my logs in Kibana. But now I want to see my logs in sessions. I hope the log lines can be grouped by session and shown in Kibana's Discover
page. In my scenario, the log lines with the same (host, client_ip)
belong to the same session.
I hope to have this:
Session table
name, client_ip, host
session1, www.google.com, 1.2.3.4
session2, www.bing.com, 5.6.7.8
session3, www.google.com, 4.3.2.1
When I click one of the above session (e.g., session1), I can see all the records of that session in the following 2nd table:
Log table
timestamp, http_method, request_uri, http_status, host, user_agent, client_ip, client_port
20181105, 21:33:17.773, POST, /index.html, 200, www.google.com, chrome 59, 1.2.3.4, 1234
20181105, 21:33:18.773, POST, /abc.html, 200, www.google.com, chrome 59, 1.2.3.4, 1234
20181105, 21:33:19.773, POST, /index.html, 404, www.google.com, chrome 59, 1.2.3.4, 5678
I know Elasticsearch does flat indexing, it's not easy to have hierarchy between documents. I'm OK to create separated indices for the above two tables. I know Dashboard can show two Discover tables at the same time. But my question is:
How to link these two tables? When I click one item in the Session table, the Log table will show corresponding contents?
Or is there any other way to fulfill my requirement (view session-based logs easily in Kibana)? Thanks.
UPDATE
The index for Log table contains the session field, which can be session1
, session2
, etc. Both indices are under my control. So I can add any field if needed.
elasticsearch kibana kibana-6
elasticsearch kibana kibana-6
edited Nov 8 at 5:38
asked Nov 8 at 4:42
Yang Luo
8211337
8211337
Does the log table/index also have a field containing the session name, i.e.session1
?
– Val
Nov 8 at 4:48
@Val yes, the index is under my control. I can add any field if needed.
– Yang Luo
Nov 8 at 4:53
add a comment |
Does the log table/index also have a field containing the session name, i.e.session1
?
– Val
Nov 8 at 4:48
@Val yes, the index is under my control. I can add any field if needed.
– Yang Luo
Nov 8 at 4:53
Does the log table/index also have a field containing the session name, i.e.
session1
?– Val
Nov 8 at 4:48
Does the log table/index also have a field containing the session name, i.e.
session1
?– Val
Nov 8 at 4:48
@Val yes, the index is under my control. I can add any field if needed.
– Yang Luo
Nov 8 at 4:53
@Val yes, the index is under my control. I can add any field if needed.
– Yang Luo
Nov 8 at 4:53
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
What I would do is to add a session
field in the log table containing the same session name as in the session table for each log line. That's going to be your "join key".
Then, you can create one sessions
index and another logs
index. Both indexes must have that session
field. Then go in Kibana and can create one index-pattern for each index.
Next, go to the Discover tab and create one saved search per index pattern, you now should have a saved search named "Logs" and another one named "Sessions".
Finally, head to the Dashboard tab and add the two saved searches you created previously. On the screenshot below, you can see that when hovering over the session field you can filter by that field. If you click on (e.g.) session2
, then both tables will be filtered accordingly, thus achieving what you need.
any luck with this?
– Val
Nov 10 at 10:28
thank you very much! This solution exactly did what I want! This is even better than what I thought, because I can filter on other fields in the "Sessions" window instead of just session ID.
– Yang Luo
Nov 22 at 3:28
Awesome, glad it helped!
– Val
Nov 22 at 5:16
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
What I would do is to add a session
field in the log table containing the same session name as in the session table for each log line. That's going to be your "join key".
Then, you can create one sessions
index and another logs
index. Both indexes must have that session
field. Then go in Kibana and can create one index-pattern for each index.
Next, go to the Discover tab and create one saved search per index pattern, you now should have a saved search named "Logs" and another one named "Sessions".
Finally, head to the Dashboard tab and add the two saved searches you created previously. On the screenshot below, you can see that when hovering over the session field you can filter by that field. If you click on (e.g.) session2
, then both tables will be filtered accordingly, thus achieving what you need.
any luck with this?
– Val
Nov 10 at 10:28
thank you very much! This solution exactly did what I want! This is even better than what I thought, because I can filter on other fields in the "Sessions" window instead of just session ID.
– Yang Luo
Nov 22 at 3:28
Awesome, glad it helped!
– Val
Nov 22 at 5:16
add a comment |
up vote
1
down vote
accepted
What I would do is to add a session
field in the log table containing the same session name as in the session table for each log line. That's going to be your "join key".
Then, you can create one sessions
index and another logs
index. Both indexes must have that session
field. Then go in Kibana and can create one index-pattern for each index.
Next, go to the Discover tab and create one saved search per index pattern, you now should have a saved search named "Logs" and another one named "Sessions".
Finally, head to the Dashboard tab and add the two saved searches you created previously. On the screenshot below, you can see that when hovering over the session field you can filter by that field. If you click on (e.g.) session2
, then both tables will be filtered accordingly, thus achieving what you need.
any luck with this?
– Val
Nov 10 at 10:28
thank you very much! This solution exactly did what I want! This is even better than what I thought, because I can filter on other fields in the "Sessions" window instead of just session ID.
– Yang Luo
Nov 22 at 3:28
Awesome, glad it helped!
– Val
Nov 22 at 5:16
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
What I would do is to add a session
field in the log table containing the same session name as in the session table for each log line. That's going to be your "join key".
Then, you can create one sessions
index and another logs
index. Both indexes must have that session
field. Then go in Kibana and can create one index-pattern for each index.
Next, go to the Discover tab and create one saved search per index pattern, you now should have a saved search named "Logs" and another one named "Sessions".
Finally, head to the Dashboard tab and add the two saved searches you created previously. On the screenshot below, you can see that when hovering over the session field you can filter by that field. If you click on (e.g.) session2
, then both tables will be filtered accordingly, thus achieving what you need.
What I would do is to add a session
field in the log table containing the same session name as in the session table for each log line. That's going to be your "join key".
Then, you can create one sessions
index and another logs
index. Both indexes must have that session
field. Then go in Kibana and can create one index-pattern for each index.
Next, go to the Discover tab and create one saved search per index pattern, you now should have a saved search named "Logs" and another one named "Sessions".
Finally, head to the Dashboard tab and add the two saved searches you created previously. On the screenshot below, you can see that when hovering over the session field you can filter by that field. If you click on (e.g.) session2
, then both tables will be filtered accordingly, thus achieving what you need.
answered Nov 8 at 5:05
Val
99.3k6127164
99.3k6127164
any luck with this?
– Val
Nov 10 at 10:28
thank you very much! This solution exactly did what I want! This is even better than what I thought, because I can filter on other fields in the "Sessions" window instead of just session ID.
– Yang Luo
Nov 22 at 3:28
Awesome, glad it helped!
– Val
Nov 22 at 5:16
add a comment |
any luck with this?
– Val
Nov 10 at 10:28
thank you very much! This solution exactly did what I want! This is even better than what I thought, because I can filter on other fields in the "Sessions" window instead of just session ID.
– Yang Luo
Nov 22 at 3:28
Awesome, glad it helped!
– Val
Nov 22 at 5:16
any luck with this?
– Val
Nov 10 at 10:28
any luck with this?
– Val
Nov 10 at 10:28
thank you very much! This solution exactly did what I want! This is even better than what I thought, because I can filter on other fields in the "Sessions" window instead of just session ID.
– Yang Luo
Nov 22 at 3:28
thank you very much! This solution exactly did what I want! This is even better than what I thought, because I can filter on other fields in the "Sessions" window instead of just session ID.
– Yang Luo
Nov 22 at 3:28
Awesome, glad it helped!
– Val
Nov 22 at 5:16
Awesome, glad it helped!
– Val
Nov 22 at 5:16
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53201662%2fhow-to-make-one-discover-table-link-to-another-discover-table-in-dashboard-or-el%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Does the log table/index also have a field containing the session name, i.e.
session1
?– Val
Nov 8 at 4:48
@Val yes, the index is under my control. I can add any field if needed.
– Yang Luo
Nov 8 at 4:53