-SGregory-

This is the response I get: As you can see, the request for the token is successful and 'access_token' contains a valid value, but trying to run the 'GET' underneath produces a 401 Unauthorized error. I've been looking at the API debug logs but its not clear at the moment what the issue is. I'll keep looking, but this is…

I thought I was nearly there when I realised I missed a step out of the chaining instructions, which was to duplicate the poller that grabs the bearer token. Supposedly when you do that and if i'm understanding it correctly, the token variable should also be duplicated and selectable from within the copied poller - but in…

Also, I see no stored values in the other poller(s). Which I can see is one of the problems....

I noticed that too. Once i've run the POST request, although that completes and I see the token returned, it never makes it to the variable. I basically have this one poller which gets the token and other pollers which I need to use that token in subsequent GET requests. They're all to Azure, if that makes any difference.

Thanks for your reply. I get what you're saying but, referencing the token as you suggest: Gives me this error: This would suggest it is being stored, right?: What am I doing wrong?

I have the same problem, nobody seems to be able to explain why (not even Solarwinds tech support!).

I'll open another thread on the SAM forum, SW tech support are unwilling/unable to help me with the query at this point. If I get nowhere with the other thread, i'll try our CSM.

Thanks Cheryl. I actually did open a ticket with support. However, they say they cannot diagnose issues with custom scripts, so it looks like i'm back to square one at this point, with a script that produces output with missing data (for reasons still unknown).

By way of an update - I spoke to SW tech support, who were not particularly helpful. It seems they won't support custom queries to SQL/SWQL and nor can they explain (or simply won't explain) why the query output differs from the pre-defined report you can run from the Orion console. Overall, very disappointing and…

No - all have volumes attached and all are Windows based servers. I'll keep looking, but its super frustrating as I really need this data for some reporting I have to produce for our senior management team. Might have to log a support ticket I guess...

No to thought 1....I assume by 'grey' you mean, are they in an 'Unknown' status? If so, thats a no too - most of the nodes have been on the system for a number of years.