andygreenough

I thought that might be the case but wanted to ensure I wasn't missing something. Thanks!

Excellent that's exactly what I needed thank you. Rather than create the extra node custom prop I believe my issue will be resolved with our upcoming SAM upgrade so I can just use * ${APM_ApplicationCustomProperties.MyProperty}

Been looking at the VolumeUsage_ForecastCoefficients table to see if I can utilise the data there but the numbers are 1 higher than those shown on the node page. i.e. I have a server which predicts > 60% in 7 months for C:\ but this query states 8 months. Does a month get removed by default or am I just way off on my…

Hi, thanks for the reply. I probably didn't explain properly. The trigger is targeting an application and I'm then running the test against a node with that application assigned to it but the test is running against another application monitor on the same node almost as if it just chooses the first it comes to on that node…

It does thank you as that's exactly the same as I have in my table. I have no idea why I'm getting those errors in the logs so I'll log a ticket

Thanks for this but are you certain only the SQL port is required? I wouldn't have thought all the component monitors use that port. I'm hoping to get permission to use the agent instead as it's a single port requirement but that's a no go at the moment as we have an agentless only policy on system monitoring.

you shouldn't need to perform a custom SQL lookup for a custom property. I think that was resolved in the previous SAM release. We have alerts working with ${N=SwisEntity;M=CustomProperties.Application_Alert_SMTP_Address} as the To address. You'd need to amend to ${N=SwisEntity;M=CustomProperties.AlertEmails} to pick up…

Does anyone have any idea how you can use the Volume Capacity Forecast report content for more than one node or how the data is calculated for use in a custom table? We'd like to report on all nodes of a service and the predicted capacity so a table like the below. Node | Volume | >60% | >80% | >100% Node1 | C:\ | > 1 year…

Another good troubleshooting step I've found is to re-run the configuration wizard. I've had modules not install correctly before or have some kind of issue and a simple re-run as sorted it.

OK I know this post is old but just in case anyone else comes across this I was having the same issue and found it was down to us using a DNS entry to access the web console. We normally use http://solarwinds to access the system and logos don't display or upload on there (so you think as you get the black box) but if I…