Is anybody else using the legacy web metering feature in SLM?

5 years ago

Thanks, we've also looked at the new feature, but we can't use it yet.

For us, we were not able to add new web applications to the legacy web metering. Well, we could add them in SLM, and the Agents would receive the updates in the webapps.config file and we would even see the metering recorded correctly in the snowpacks. But when Snow Inventory processes the snowpack it will only add new rows to the inv.DataWebApplication table with WebApplicationIds 1,2,3, etc... And since there already will be rows with those WebApplicationIds then nothing gets added and that's the end of it, no detections would show up and get transferred by the DUJ. It looks like a Snow Inventory problem.

So, we find that if we artificially keep the first few WebApplicationIds (1,2,3, etc) clear, then new web applications will get added and it all works perfectly. It's almost like Snow Inventory has been hardcoded to only add new web applications starting from a WebApplicationId of 1.

With a simple bit of SQL we can make sure everything works. I was just wondering if we're the only people to experience this problem.

Expand Post

ColinHardie
5 years ago
Hi David,
We have used it to a limited extent and it appears to work. When I initially tested it, I came across an issue, that I tried to get to the bottom of here. I also raised a ticket (Case number 04464367).

Not sure what issues you are facing but it certainly seems like its being phased out in favour of the standard web metering feature. This post mentions an internal tool that may allow end users to bypass DIS team and add their own rules but I have never seen or used it. If supported it would probably allow us to add our own internal web application URLs to be monitored and finally put the legacy option to bed.

Expand Post
- DavidH
  5 years ago
  Thanks, we've also looked at the new feature, but we can't use it yet.
  
  For us, we were not able to add new web applications to the legacy web metering. Well, we could add them in SLM, and the Agents would receive the updates in the webapps.config file and we would even see the metering recorded correctly in the snowpacks. But when Snow Inventory processes the snowpack it will only add new rows to the inv.DataWebApplication table with WebApplicationIds 1,2,3, etc... And since there already will be rows with those WebApplicationIds then nothing gets added and that's the end of it, no detections would show up and get transferred by the DUJ. It looks like a Snow Inventory problem.
  
  So, we find that if we artificially keep the first few WebApplicationIds (1,2,3, etc) clear, then new web applications will get added and it all works perfectly. It's almost like Snow Inventory has been hardcoded to only add new web applications starting from a WebApplicationId of 1.
  
  With a simple bit of SQL we can make sure everything works. I was just wondering if we're the only people to experience this problem.
  Expand Post

Related Product Forums