Are you able to assign a web application url to an agreement, only when there has been activity to said url?
I have never assigned a web application to an agreement, so I cannot categorically answer your question, however I do know that when I define a new URL for monitoring, it does not appear in the all applications list until after it has actually detected some usage, so I would assume that you cannot assign it to anything until it has had usage reported.
Hello Mark - thanks for the thoughts, as that was what I was thinking also.
Hi both,I've found the same as the above, that the application doesn't show until the URL has some sort of metering information. Once you do have the details, doesn't it then act as just another application? Must admit, I haven't had any usage from it yet!Best,David
David - yes, that is how I use it, as another application. I add it to the agreement, accordingly. Thanks.
Hi all,I can see that you all can define and meter web applications.I also tried to do that in SLM, but only got results, when I defined a webapplication in our internal network.But there was no result, when I created a internet webapplication.We are using proxies for internet connection and Snow always told me, then it's not possible to meter a webapplication.Don't you use a proxy or how did you solve that?
I have tried to register a web application before and after carola.iberl note about the internal site just added an internal URL (we are no longer using proxy servers). I have visited but internal and external sites but still not seeing any application for them. Can anyone provide any hints on setting these up and what i should see in SLM?
I was halfway through typing a big explanation of how it all works with screen shots and everything, then I came across an article on the Snow Knowledgebase that has it all covered.
If you have a snow support portal account, login to the portal and search for KB0013022
If you still have questions after looking at that, let me know
Dont you just hate it when that happens!!! Thanks for the thought and the KB, will check that out now!
Just found the KB but there doesnt seem to be a document attached just details of whats in the document?
Not sure of this works in the new support portal, but try this link. https://snowprod.service-now.com/support/sys_attachment.do?sys_id=ca63e5370f9f6a002944f88ce1050e9f&sysparm_viewer_table=kb_knowledge&sysparm_viewer_id=c3f2e9370f9f6a002944f88ce1050e27&view=true
Perfect, downloaded the doc files so will have a little read.
Well the good news is one of the URL's is being seen as a web application, just not things like dropbox.com or aws.amazon.com even though i have been to these sites its not registering them.
Duncan - interesting, as it looks like the URL dropbox.com is simple enough to get registered traffic for usage. Open a ticket with Snow to confirm your URL settings and to check a local file that collects that information. Just a thought.
To clarify a little bit, when the SRS team assigns rules to a SaaS application, there a 3 parts of a full URL that we track.
A generic URL is of the form:
What is important to Snow is the following.
Scheme - e.g. https, http, ftp, file, etc...
Host - e.g. salesforce.com, agilecrm.com, atlassian.net
Path - e.g. /api, /core/api, /backend, /admin, /home etc...
These 3 components do not contain any private data from customers, so we will not be tracking sensitive data.
The path is what allows us to make sure that SaaS metering is only begun, once the user has entered valid credentials and logged into the SaaS application. Without the path, we would begin tracking from the moment a user lands on the login page, and this would report a false usage for anyone who reaches this page without being an actual user.
Hopefully this clears up some questions some people may have.
Hi Ben. This makes things so much clearer, so thanks for the info!
Ben - when adding a URL, is the "Scheme" necessary? Will usage be captured with just salesforce.com? Thanks.
In our config we dont specify the Scheme as defined above, our pattern is just defined as salesforce.com and we are reporting usage data from that.
Hi Randy & Mark,My apologies for not clarifying, I was referring to the 2017:2 release of global cloud normalisation and metering. The scheme will be necessary for the upcoming release to track globally. But I can see now, that you are talking about locally added web applications.
Being apart of the SRS, I cant say I have had that much experience with adding web applications locally in the customer's environment. This is usually managed by the regional support teams who will have a more definitive answer for you.Best regards,Ben
That is very useful info, but is that related to the current Web Applications that we can add to SLM via the administration page, or are you refering to the up and coming SaaS release where the DIS team are publishing a list of know SaaS applications into Snow so the Inventory 5 agent will identify and track them as standard applications?
I was under the impression that with the current product version we should not specify the Scheme or Path and should just add the Host as the pattern in the web application definition. I believe I was told if we added a path for example, the rule would stop working.
Hello - also, for proxy issues, our network team just made exceptions if needed.
Also for the 'traditional' web app monitoring see How to troubleshoot Webapp Monitoring
With the 2017:2 release, the Inventory 5 agent will do SAAS monitoring - which is a completely different (and additional) way of monitoring, as mentioned by benjamin.van.dam
Retrieving data ...