Logscape Support

Members Login
Username 
 
Password 
    Remember Me  
Logscape Support -> logscape -> Workspace linking filters not passing to Maps
Post Info TOPIC: Workspace linking filters not passing to Maps
kelv1n


Member

Status: Offline
Posts: 16
Date:
Workspace linking filters not passing to Maps
Permalink  
 

Hi

I've got a Workspace called "Firewall - Security" which has a HTML menu and 2 maps. The HTML menu has 3 links back to the same workspace, just with different Filter options passed to it, the idea is this allows me to filter the traffic by each of our different Firewalls host IP. The HTML options are as follows

  • Display All - http://10.50.100.186:8080/play/?Workspace=Security%20-%20Firewalls&filter=&filterAction=
  • Display FW1 - http://10.50.100.186:8080/play/?Workspace=Security%20-%20Firewalls&filter=10.0.100.1&filterAction=_host.equals
  • Display FW2 - http://10.50.100.186:8080/play/?Workspace=Security%20-%20Firewalls&filter=10.100.100.1&filterAction=_host.equals

The query this is running is

*|_tag.equals(fortigate) srcintf.equals(wan1) geoip_src.count(,country) geoip_src_city.count(,city) chart(map) buckets(1)

When filtered via the URL, the query should look like

*|_tag.equals(fortigate) srcintf.equals(wan1) geoip_src.count(,country) geoip_src_city.count(,city) chart(map) buckets(1) _host.equals(10.0.100.1)

But I don't think the _host.equals is getting applied.. If I click "Click to Drilldown" then it works and i can see the query in the search bar and the content is correctly filtered.

 

Any thoughts on this? Am I doing something wrong?

 



-- Edited by kelv1n on Friday 23rd of October 2015 09:40:36 AM



-- Edited by kelv1n on Friday 23rd of October 2015 09:50:50 AM

__________________
neilson9


Senior Member

Status: Offline
Posts: 100
Date:
Permalink  
 

Hi Kelvin,

Would you be able to export your config and .zip your data then send it to support? If not - no problems - then we will work around it.

Regards,
Na.

__________________
neilson9


Senior Member

Status: Offline
Posts: 100
Date:
Permalink  
 

Kelvin - we have made progress on this problem. We could issue you a patch? Are you updated to 3.01?

__________________
kelv1n


Member

Status: Offline
Posts: 16
Date:
Permalink  
 

Hi

I'm still on v3.0, but this is still a test install, so I'd be happy just to do a full upgrade if that helps?

__________________
neilson9


Senior Member

Status: Offline
Posts: 100
Date:
Permalink  
 

We should be making some further progress this week - just finalising 3.02 the performance release.

Regards,
Na.

__________________
kelv1n


Member

Status: Offline
Posts: 16
Date:
Permalink  
 

Hi

Just wondering if there was any news on this?

Cheers


__________________
neilson9


Senior Member

Status: Offline
Posts: 100
Date:
Permalink  
 

Hi,
Sorry no, we have it in the radar but other items have cropped up.

Planning on getting to it this or next week.

Cheers,
Neil.

__________________
neilson9


Senior Member

Status: Offline
Posts: 100
Date:
Permalink  
 

Pls take a look at 3.03 - filtering should work as expected.

Note:
* |_tag.equals(fortigate) srcintf.equals(wan1) geoip_src.count(,country) geoip_src_city.count(,city) chart(map) buckets(1)
will be faster as:
wan1 |_tag.equals(fortigate) srcintf.equals(wan1) geoip_src.count(,country) geoip_src_city.count(,city) chart(map) buckets(1)

Regards,
Neil.

__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.
Logscape Support -> logscape -> Workspace linking filters not passing to Maps


Create your own FREE Forum
Report Abuse 		Powered by ActiveBoard