All Posts

Find Answers
Ask questions. Get answers. Find technical product solutions from passionate members of the Splunk community.

All Posts

Hi @dinesh001kumar, In Simple XML and without resorting to custom HTML, CSS, and JavaScript in separate files, you can use a visualization to draw circles and drilldowns to control the visibility of... See more...
Hi @dinesh001kumar, In Simple XML and without resorting to custom HTML, CSS, and JavaScript in separate files, you can use a visualization to draw circles and drilldowns to control the visibility of rows or panels. Here's an (ugly) example using six rows of five single value panels controlled by a separate table panel: <dashboard version="1.1" theme="light"> <label>pagination</label> <init> <set token="show_page_1_tok">1</set> <set token="page_1_tok">⬤</set> <unset token="show_page_2_tok"></unset> <set token="page_2_tok">◯</set> <unset token="show_page_3_tok"></unset> <set token="page_3_tok">◯</set> <unset token="show_page_4_tok"></unset> <set token="page_4_tok">◯</set> <unset token="show_page_5_tok"></unset> <set token="page_5_tok">◯</set> <unset token="show_page_6_tok"></unset> <set token="page_6_tok">◯</set> </init> <row depends="$show_page_1_tok$" rejects="$show_page_2_tok$,$show_page_3_tok$,$show_page_4_tok$,$show_page_5_tok$,$show_page_6_tok$"> <panel> <single> <search> <query>| stats count | eval count=1</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=1</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=1</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=1</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=1</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> </row> <row depends="$show_page_2_tok$" rejects="$show_page_1_tok$,$show_page_3_tok$,$show_page_4_tok$,$show_page_5_tok$,$show_page_6_tok$"> <panel> <single> <search> <query>| stats count | eval count=2</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=2</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=2</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=2</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=2</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> </row> <row depends="$show_page_3_tok$" rejects="$show_page_1_tok$,$show_page_2_tok$,$show_page_4_tok$,$show_page_5_tok$,$show_page_6_tok$"> <panel> <single> <search> <query>| stats count | eval count=3</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=3</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=3</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=3</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=3</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> </row> <row depends="$show_page_4_tok$" rejects="$show_page_1_tok$,$show_page_2_tok$,$show_page_3_tok$,$show_page_5_tok$,$show_page_6_tok$"> <panel> <single> <search> <query>| stats count | eval count=4</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=4</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=4</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=4</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=4</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> </row> <row depends="$show_page_5_tok$" rejects="$show_page_1_tok$,$show_page_2_tok$,$show_page_3_tok$,$show_page_4_tok$,$show_page_6_tok$"> <panel> <single> <search> <query>| stats count | eval count=5</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=5</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=5</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=5</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=5</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> </row> <row depends="$show_page_6_tok$" rejects="$show_page_1_tok$,$show_page_2_tok$,$show_page_3_tok$,$show_page_4_tok$,$show_page_5_tok$"> <panel> <single> <search> <query>| stats count | eval count=6</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=6</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=6</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=6</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> <panel> <single> <search> <query>| stats count | eval count=6</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">none</option> </single> </panel> </row> <row> <panel> <html> <style> #page_table thead { visibility: collapse !important; } </style> </html> <table id="page_table"> <search> <query>| makeresults | fields - _time | eval "Page 1"="$page_1_tok$", "Page 2"="$page_2_tok$", "Page 3"="$page_3_tok$", "Page 4"="$page_4_tok$", "Page 5"="$page_5_tok$", "Page 6"="$page_6_tok$"</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <option name="drilldown">cell</option> <option name="wrap">false</option> <drilldown> <condition field="Page 1"> <set token="show_page_1_tok">1</set> <set token="page_1_tok">⬤</set> <unset token="show_page_2_tok"></unset> <set token="page_2_tok">◯</set> <unset token="show_page_3_tok"></unset> <set token="page_3_tok">◯</set> <unset token="show_page_4_tok"></unset> <set token="page_4_tok">◯</set> <unset token="show_page_5_tok"></unset> <set token="page_5_tok">◯</set> <unset token="show_page_6_tok"></unset> <set token="page_6_tok">◯</set> </condition> <condition field="Page 2"> <unset token="show_page_1_tok"></unset> <set token="page_1_tok">◯</set> <set token="show_page_2_tok">1</set> <set token="page_2_tok">⬤</set> <unset token="show_page_3_tok"></unset> <set token="page_3_tok">◯</set> <unset token="show_page_4_tok"></unset> <set token="page_4_tok">◯</set> <unset token="show_page_5_tok"></unset> <set token="page_5_tok">◯</set> <unset token="show_page_6_tok"></unset> <set token="page_6_tok">◯</set> </condition> <condition field="Page 3"> <unset token="show_page_1_tok"></unset> <set token="page_1_tok">◯</set> <unset token="show_page_2_tok"></unset> <set token="page_2_tok">◯</set> <set token="show_page_3_tok">1</set> <set token="page_3_tok">⬤</set> <unset token="show_page_4_tok"></unset> <set token="page_4_tok">◯</set> <unset token="show_page_5_tok"></unset> <set token="page_5_tok">◯</set> <unset token="show_page_6_tok"></unset> <set token="page_6_tok">◯</set> </condition> <condition field="Page 4"> <unset token="show_page_1_tok"></unset> <set token="page_1_tok">◯</set> <unset token="show_page_2_tok"></unset> <set token="page_2_tok">◯</set> <unset token="show_page_3_tok"></unset> <set token="page_3_tok">◯</set> <set token="show_page_4_tok">1</set> <set token="page_4_tok">⬤</set> <unset token="show_page_5_tok"></unset> <set token="page_5_tok">◯</set> <unset token="show_page_6_tok"></unset> <set token="page_6_tok">◯</set> </condition> <condition field="Page 5"> <unset token="show_page_1_tok"></unset> <set token="page_1_tok">◯</set> <unset token="show_page_2_tok"></unset> <set token="page_2_tok">◯</set> <unset token="show_page_3_tok"></unset> <set token="page_3_tok">◯</set> <unset token="show_page_4_tok"></unset> <set token="page_4_tok">◯</set> <set token="show_page_5_tok">1</set> <set token="page_5_tok">⬤</set> <unset token="show_page_6_tok"></unset> <set token="page_6_tok">◯</set> </condition> <condition field="Page 6"> <unset token="show_page_1_tok"></unset> <set token="page_1_tok">◯</set> <unset token="show_page_2_tok"></unset> <set token="page_2_tok">◯</set> <unset token="show_page_3_tok"></unset> <set token="page_3_tok">◯</set> <unset token="show_page_4_tok"></unset> <set token="page_4_tok">◯</set> <unset token="show_page_5_tok"></unset> <set token="page_5_tok">◯</set> <set token="show_page_6_tok">1</set> <set token="page_6_tok">⬤</set> </condition> </drilldown> </table> </panel> </row> </dashboard>  
WoW!!  Your example got me super close to the finish line!!! The only issue left is that when I have "All" selected with other options and then unselect other options so that only the "All" option... See more...
WoW!!  Your example got me super close to the finish line!!! The only issue left is that when I have "All" selected with other options and then unselect other options so that only the "All" option remains, then the "app_net_fm_entity_id" token gets unset, instead of having the value of "_all" <input id="app_nodes_multiselect" type="multiselect" depends="$app_fm_app_id$" token="app_fm_entity_id" searchWhenChanged="true"> <label>Nodes</label> <delimiter> </delimiter> <fieldForLabel>entity_name</fieldForLabel> <fieldForValue>internal_entity_id</fieldForValue> <search> <query> | inputlookup aix_kv_apm_comps WHERE entity_type!=$app_fm_group_nodes$ | search [| makeresults | eval search="internal_parent_id=(".mvjoin($app_fm_app_id$, " OR internal_parent_id=").")" | return $search] | table entity_name, internal_entity_id | sort entity_name </query> </search> <choice value="*">All</choice> <default>*</default> <change> <condition match="$form.app_fm_entity_id$=&quot;*&quot;"> <eval token="app_net_fm_entity_id">_all</eval> </condition> <condition> <eval token="app_net_fm_entity_id">case(mvcount($form.app_fm_entity_id$)="2" AND mvindex($form.app_fm_entity_id$,0)="*", mvindex($form.app_fm_entity_id$,1), mvfind($form.app_fm_entity_id$,"^\\*$$")=mvcount($form.app_fm_entity_id$)-1, "_all", true(), $form.app_fm_entity_id$)</eval> </condition> </change> </input>      
Thank you so much for your help!!! I apologize that I wasn't completely clear in my requirement. I need the "app_net_fm_entity_id" token set to "_all" IF the "app_fm_entity_id" (aka selectedvalues)... See more...
Thank you so much for your help!!! I apologize that I wasn't completely clear in my requirement. I need the "app_net_fm_entity_id" token set to "_all" IF the "app_fm_entity_id" (aka selectedvalues) has only the "*" value selected. A different way to say that is, I need the "app_net_fm_entity_id" token set to "_not_star_but_other" IF the "app_fm_entity_id" (aka selectedvalues) has only the "*" value selected.  
@ITWhisperer Yes, env and tenant are already extracted, yes, we need stat broken by env and tenant as well as time   {"datetime":"08-19-2024 10:40:30.196 +1000","log_level":"INFO","component":"... See more...
@ITWhisperer Yes, env and tenant are already extracted, yes, we need stat broken by env and tenant as well as time   {"datetime":"08-19-2024 10:40:30.196 +1000","log_level":"INFO","component":"Hostwide","data":{"cpu_arch":"x86_64","os_name":"Linux","os_name_ext":"Linux","os_build":"#1 ABC Thu Apr 4 03:33:23 EDT 2024","os_version":"3.10.0-1160.118","instance_guid":"ABCDEFGH","splunk_version":"9.2.1","mem":"382641.051","mem_used":"41983.578","swap":"511.996","swap_used":"511.996","pg_paged_out":"50842005897","pg_swapped_out":"164124","forks":"00000600","cpu_count":"24","virtual_cpu_count":"48","runnable_process_count":"19","normalized_load_avg_1min":"1.14","cpu_user_pct":"45.35","cpu_system_pct":"10.68","cpu_idle_pct":"43.98"}}  
Yes, thank you. On top of creating those two separate tables. I want to then store the table data in separate indexes and maintaining all fields headers and values. From there I want to restrict acce... See more...
Yes, thank you. On top of creating those two separate tables. I want to then store the table data in separate indexes and maintaining all fields headers and values. From there I want to restrict access to the indexes. Ideally, I want to avoid creating separate apps
1. The use case is ideally I just want to create separate indexes based on a search filter and be able to restrict access to these filters based on roles without the need to create different apps. Th... See more...
1. The use case is ideally I just want to create separate indexes based on a search filter and be able to restrict access to these filters based on roles without the need to create different apps. The data I'm ingesting is aggregate so only admins can see it. From there, I want to create two separate dashboards (not Splunk apps if possible) showing data for superheros or villains. I need only users with the role "good guys" to access the superhero dashboard and be unable to access the villain dashboard and vice versa. The solution I've thought about is by creating indexes which only differ by one line (e.g. archetype=superhero/villain) and then restricting access to these indexes based on user roles. 2. I can't restrict access when using search-time filters though. 3. Okay I understand summary indexing is not the best approach. Do you have a better solution
Arrows are an attribute of lines.  They don't show up, however, until you increase the thickness of the line.  
Yes, I've thought about creating different apps but I wanted to avoid this since the only difference between the apps will be one line in the filter (e.g. archetype="superhero"). Ideally I just want ... See more...
Yes, I've thought about creating different apps but I wanted to avoid this since the only difference between the apps will be one line in the filter (e.g. archetype="superhero"). Ideally I just want to create separate indexes based on a search filter and be able to restrict access to these filters based on roles without the need to create different apps. I tried populating the summary index using the query above. By Original Fields not populating, I mean once you run the query and check the index that was created (e.g. index=superheros), the fields present in the search don't include id, strengths, and archetype but only default fields like date_hour, index, timeendpos etc).
You can't use $value$ and your <condition> elements are wrong - I assume you're trying to make a conditional expression, however, you just have effectively a single condition This is the technique t... See more...
You can't use $value$ and your <condition> elements are wrong - I assume you're trying to make a conditional expression, however, you just have effectively a single condition This is the technique to remove all and add all when using multiselect <change> <condition match="$form.app_fm_entity_id$=&quot;*&quot;"> <eval token="form.app_fm_entity_id">*</eval> </condition> <condition> <eval token="form.app_fm_entity_id">case(mvcount($form.app_fm_entity_id$)="2" AND mvindex($form.app_fm_entity_id$,0)="*", mvindex($form.app_fm_entity_id$,1), mvfind($form.app_fm_entity_id$,"^\\*$$")=mvcount($form.app_fm_entity_id$)-1, "*", true(), $form.app_fm_entity_id$)</eval> </condition> </change>  It will set the token to * not _all because that is the value defined in your default 'All' option.  
Might be a silly question but does anyone possibly know where I can locate lines with pointing arrows at the end? I wanted to use them to point to each panel I had to show a flow diagram of some sort.
I am using the multiselect input definition below: The issue is that it is not setting the token named "app_net_fm_entity_id" properly. The desired behavior is, if the user selects "All" label ... See more...
I am using the multiselect input definition below: The issue is that it is not setting the token named "app_net_fm_entity_id" properly. The desired behavior is, if the user selects "All" label (value=*) then the condition should detect the "*" value and set the "app_net_fm_entity_id" token to "_all" If the user selects anything else other than just the "All" label then the "app_net_fm_entity_id" token should be set to the contents of the selected values. I am using Splunk Enterprise 9.2.1 This is a simple xml dashoard, aka classic dashboard. I am 1month into splunk and learning feverishly but I surely need some help on this.  I've tried using JS to get the desired behavior for this multi, but couldn't get that to work either     <input id="app_nodes_multiselect" type="multiselect" depends="$app_fm_app_id$" token="app_fm_entity_id" searchWhenChanged="true"> <label>Nodes</label> <delimiter> </delimiter> <fieldForLabel>entity_name</fieldForLabel> <fieldForValue>internal_entity_id</fieldForValue> <search> <query> | inputlookup aix_kv_apm_comps WHERE entity_type!=$app_fm_group_nodes$ | search [| makeresults | eval search="internal_parent_id=(".mvjoin($app_fm_app_id$, " OR internal_parent_id=").")" | return $search] | table entity_name, internal_entity_id | sort entity_name </query> </search> <choice value="*">All</choice> <default>*</default> <change> <condition> <eval>len($value$) == 1</eval> <set token="app_net_fm_entity_id">_all</set> </condition> <condition> <eval>len($value$) > 1</eval> <set token="app_net_fm_entity_id">$value$</set> </condition> </change> </input>                
Well, you need to simply find something between your "anchors". Which in simplest form might just be stringstart\s(?<uuid>.*)\sstringend If you know that the uuid has some particular form you can b... See more...
Well, you need to simply find something between your "anchors". Which in simplest form might just be stringstart\s(?<uuid>.*)\sstringend If you know that the uuid has some particular form you can be a bit more specific (for example not to capture wrongly formed uuid) stringstart\s(?<uuid>[0-9a-f]-[0-9a-f]{8}-(?:[0-9a-f]{4}-){3}[0-9a-f]{12})\sstringend You can even add more anchoring text in front or at the end if you have more constant parts. So as you have a regex matching and extracting this part, you can - depending on your use case - either use it as @marnall showed with rex command or use it to define a search-time extraction. For example EXTRACT-uuid = stringstart\s(?<uuid>[0-9a-f]-[0-9a-f]{8}-(?:[0-9a-f]{4}-){3}[0-9a-f]{12})\sstringend
Hi @tuts, Use Elasticsearch Data Integrator - Module Input if your requirements match the following: Simple index list or pattern Single date field Less than or equal to 10,000 documents per sea... See more...
Hi @tuts, Use Elasticsearch Data Integrator - Module Input if your requirements match the following: Simple index list or pattern Single date field Less than or equal to 10,000 documents per search The add-on uses the Python Elasticsearch client search() method, which wraps the Elasticsearch Search API. The add-on will search for all documents in the configured index list with configured date field values greater than or equal to now minus the configured offset and less than or equal to now. E.g. Given logs-*,metrics-*, @timestamp, and -24h, respectively, the add-on will retrieve documents in pages of 1,000: GET /logs-*,metrics-*/_search?from=0&size=1000 { "query": { "bool": { "must": [ { "range": { "@timestamp": { "gte": "now-24h", "lte": "now" } } } ] } } } Elasticsearch limits scrolling using the from and size parameters to 10,000 results (10 pages of 1,000 documents). If you need to retrieve more documents per interval or need more control over how search results are presented prior to entering the Splunk ingest pipeline, you should evaluate REST API Module Input or similar solutions. You might also consider writing your own modular input or scripted input. A custom solution would allow to control the query language (Query DSL, ES|QL, SQL, etc.), scrolling, checkpointing, etc. If you have more specific questions, members of the community like me with experience in both Splunk and Elasticsearch can assist.
Hi @sjlaplac, To change the width of inputs move them from "Above canvas" to "In canvas" and arrange them as needed. See https://docs.splunk.com/Documentation/Splunk/9.2.1/DashStudio/inputConfig#Inp... See more...
Hi @sjlaplac, To change the width of inputs move them from "Above canvas" to "In canvas" and arrange them as needed. See https://docs.splunk.com/Documentation/Splunk/9.2.1/DashStudio/inputConfig#Inputs_in_the_canvas for more information.
There can be a small problem: the error message, or "invalid message fields, wrong message from ds" as prefaced in the raw message, is a JSON array.  You want to handle that as an entity. | rex "^[^... See more...
There can be a small problem: the error message, or "invalid message fields, wrong message from ds" as prefaced in the raw message, is a JSON array.  You want to handle that as an entity. | rex "^[^{]+(?<response>.+)" | spath input=response | rename messageType as topMessageType ``` handle namespace conflict ``` | rex field=statusMessage "^[^\[]+(?<message_from_ds>[^\]]+\])" | spath input=message_from_ds path={} | mvexpand {} | spath input={} | dedup errorDetail | table errorDetail
@mistydennis  ### Steps to Use Single Value Visualization in your dashboard. 1. **Run the Query**: Use the query you provided to generate the `OnTarget` value. 2. **Select Visualization**: - Afte... See more...
@mistydennis  ### Steps to Use Single Value Visualization in your dashboard. 1. **Run the Query**: Use the query you provided to generate the `OnTarget` value. 2. **Select Visualization**: - After running the query, go to the **Visualization** tab in the search results. - From the available visualizations, choose **Single Value**. 3. **Configure Conditional Coloring**: - Click on **Format** in the Visualization tab. - Under **Color**, enable **Color by value**. - Add your conditions: - **If value is "Yes"**: Set the color to green. - **If value is "No"**: Set the color to red. 4. **Save and Use**: - Apply the settings, and you will see the value displayed either in green or red based on the result ("Yes" or "No"). - You can then save this as part of your dashboard if needed. upvote is appreciated.
I am not sure specifically what you want to do, but if you have that _raw data in an event, and you would like to extract the uuid into a field, then you can make a regex with a named capture group i... See more...
I am not sure specifically what you want to do, but if you have that _raw data in an event, and you would like to extract the uuid into a field, then you can make a regex with a named capture group in the rex command to extract it during search time. If you would like this to be permanent then you can copy the regex into a Field Extraction. <yoursearch> | rex field=_raw "com.companyname.package: (stringstart\s)?(?<uuid>\S+) (stringend )?for" I made the assumptions that there are no space characters in the uuid string, and that it is surrounded by "com.companyname.package: and "for"
Here is the raw text -  com.companyname.package: stringstart e-38049e11-72b7-4968-b575-ecaa86f54e02 stringend for some.datahere with status FAILED, Yarn appId application_687987, Yarn state FINISH... See more...
Here is the raw text -  com.companyname.package: stringstart e-38049e11-72b7-4968-b575-ecaa86f54e02 stringend for some.datahere with status FAILED, Yarn appId application_687987, Yarn state FINISHED, and Yarn finalStatus FAILED with root cause: samppleDatahere: com.packagenamehere: Forbidden (Service: Amazon S3; Status Code: 403; Error Code: 403 Forbidden; Request ID: sjhdjksdn;  Need to list down the uuid which is in between stringstart and stringend 
While you have clearly shown your search (which by the way seems perfectly fine), what you haven't shown or described is what you have tried in your dashboard. Please can you provide further informat... See more...
While you have clearly shown your search (which by the way seems perfectly fine), what you haven't shown or described is what you have tried in your dashboard. Please can you provide further information?
OK. If you found a way to feel offended, well that was not my intention. I just wanted to point out that what you were doing in this thread was counterproductive and it was indeed simply impossible t... See more...
OK. If you found a way to feel offended, well that was not my intention. I just wanted to point out that what you were doing in this thread was counterproductive and it was indeed simply impossible to help you this way. Want to help us help you? Fine, do so - check your sources and verify what was already suggested in this thread. Want to just take offense? Well, I'm trully sorry to hear that because we're really trying to create an overally friendly atmosphere here. And again - it was not my intention to make you personally feel bad. The intention was to point out that doing random things and just "splashing" random bits of information you will not get a reasonable answer because it's simply impossible. That's all. Hope you still have fun on Answers.