I have the workbook attached in the below link.
I have 3 Dashboard, 1 and 2 is the source and 3 is the target. When I click on any numbers in the Dashboard 1 or 2 or even drill down the Dashboard 1 and 2 using filters the same result underlying data should come in the Dashboard 3.
I have a filter "Region" in Dashboard 1 and 2 and whenever I use this filter the target data is not getting filtered based on Region.
I don't want to make the Region filter a global one since the user may want to see different regions in dashboard 1 and 2 simultaneously.
Is there a solution for this?
I recently tried to develop SNOW, so I need your help :-)
I created a Catalog Item and from the cmdb_ci_server table I extracted the list of operating systems [Type="Variable Lookup Select Box" and Name = os]; then I created a variable [Type="Reference" and Name = server] with the following Reference Qualifier "javascript: 'os =' + current.variables.os;".
At this point I need to automatically fill the field IP ADDRESS [Name = ip_address] with the value of the IP from cmdb_ci_server for the selected server.
I ask you how to do this and what is the type of variable to use for create the field ip_address [Single Line Text or others .....]
Thanks in advance,
I appreciate your help
Sounds like maybe you could use a Catalog UI Policy with a condition which checks for when another field's value changes. And then in the script, set the value of the ip address field.
Also, there is a variable type for IP addresses.
I am trying to allow the user to search on any of 4 criteria and have the rest of the 3 remaining field data validate based on the first search for selection.
I have four fields that I am trying to make dependent drop downs for the remaining 3 based on what you search for 1st. For example:
Scenario 1 - I search the data range validation for NAME and select a name in Cell L2.
I want the Phone, Email and Address to become dependent on the name was chosen (as there may be multiple records with the name of the person chosen).
I have accomplished this by using a secondary filter formula to filter address based on the name chosen and then applied data validation from the filter.
My problem is that I can't seem to figure out how to do the same thing if they pick the address first. Because my data validation is set on the filtered values and not the entire database. If they picked the address first, I want to validate based on ALL addresses and then filter-validate the NAME, PHONE and EMAIL.
I really just want them to be able to search whatever of the 4 criteria and then validate the other 3 on that result.
Any thoughts would help.
You can see my formula for filtering Addresses based on the Name selection in Cell S2 of the Customer Record Tab.
=if(L6="Address",filter('Sample Data'!$C:$C,'Sample Data'!$E:$E=L6),IF(L6="Phone",filter('Sample Data'!$C:$C,'Sample Data'!$D:$D=L3),IF(L6="Email",filter('Sample Data'!$C:$C,'Sample Data'!$J:$J=L4),L2)))
https://docs.google.com/spreadsheets/d/1E7adi88aEgvdV4ao8unbMHgZLEyu5CCRdTOjv8thjtc/edit#gid=1427488050
Select Name and only the Phones, Emails and Addresses for that selected name can be selected.
Select the Address and only the Names, Phones and Emails for that Address can be selected.
Same for Phone and for Email
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.
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.
Is it possible to get count of users in one group with opendj sdk?
e.g. my group has multi-values UniqueMember attribute, but is it possible that I get the count of the UniqueMember? because I don't want to list all the users, just to get the count.
Thanks
Unfortunately, there is no standard in LDAP to retrieve the number of values of an attribute of a given entry.