SLM - Web applications

8 years ago

The webapp metering data ends up in one of the encrypted .json files in the data folder, so it is not entirely easy to track that client side. But the fact that you have the webapps.config is a good start, at least the patterns are communicated to the agent. In this situation when you still do not see any results in SLM, the issue is usually one of these three: 1. As Sebastiano says, customer is using a proxy. The problem with this is that the agent will not see the endpoint URL, (samportal.xxxxxxx.nl) , it will only see that traffic is coming and going to the proxy server. 2. The pattern is not set up correctly. samportal.xxxxxxx.nl looks good to me, but http:// samportal.xxxxxxx.nl is not valid , samportal.xxxxxxx.nl/test/index.html is not, and samportal.xxxxxxx.nl:443 is not. 3. The site being tracked is not on the standard ports 80 or 443. If it uses another port it needs to be added to the list of ports in SMACC -> Basic Settings - > Web Ports. Note that if you add new ports here, you also have to specify the default ports, otherwise they will be ignored. For example if you want to add port 8080 you will have to add 80,443,8080 to this setting. Finally, if you jack up the log level for the agent to highest possible it will actually report if it finds a website that matches one of your patterns. At agent startup it should mention all patterns it is configured to look for, and then later on when you start browsing, it will report to the agent log if the addresses found matches a pattern or not. Super important here is that the browser needs to be shut down and not started again before the agent is restarted. The Agent is unable to meter ANY usage of applications that is already running when the agent starts.

Expand Post

Viktors
8 years ago
Hi ‌, Please, check the following report "All applications" with a criteria Web application equals to Yes: Best regards, Viktors
Expand Post
- rswain
  8 years ago
  Also, is this manual work still needed, using the new 5.3 Snow agent? Thanks.
  Expand Post
  - Viktors
    8 years ago
    Manual work is needed if you want to add and track your own web applications. However, Snow recognizes a lot of cloud applications, which are populated through the DIS rules (with regular updates) Regards, Viktors
    Expand Post
Sebastiano Bonfiglio (Flexera Software)
8 years ago
Hi Richard, Do you make use of a proxy server? What happens if you add a local intranet web application, is this showing up? Best, Sebastiano
Expand Post
- rhalmans
  7 years ago
  Hi Sebastiano, We do not have a proxy server installed!, Greets, Richard
  Expand Post
Portal User
8 years ago
The webapp metering data ends up in one of the encrypted .json files in the data folder, so it is not entirely easy to track that client side. But the fact that you have the webapps.config is a good start, at least the patterns are communicated to the agent. In this situation when you still do not see any results in SLM, the issue is usually one of these three: 1. As Sebastiano says, customer is using a proxy. The problem with this is that the agent will not see the endpoint URL, (samportal.xxxxxxx.nl) , it will only see that traffic is coming and going to the proxy server. 2. The pattern is not set up correctly. samportal.xxxxxxx.nl looks good to me, but http:// samportal.xxxxxxx.nl is not valid , samportal.xxxxxxx.nl/test/index.html is not, and samportal.xxxxxxx.nl:443 is not. 3. The site being tracked is not on the standard ports 80 or 443. If it uses another port it needs to be added to the list of ports in SMACC -> Basic Settings - > Web Ports. Note that if you add new ports here, you also have to specify the default ports, otherwise they will be ignored. For example if you want to add port 8080 you will have to add 80,443,8080 to this setting. Finally, if you jack up the log level for the agent to highest possible it will actually report if it finds a website that matches one of your patterns. At agent startup it should mention all patterns it is configured to look for, and then later on when you start browsing, it will report to the agent log if the addresses found matches a pattern or not. Super important here is that the browser needs to be shut down and not started again before the agent is restarted. The Agent is unable to meter ANY usage of applications that is already running when the agent starts.
Expand Post