Comments
-
Your flow source is the interface that sends to solarwinds... so what IP Address will actually send the flow data to your solarwinds poller. I think you're confusing this with determining which interfaces will be monitored for usage.
-
My understanding is they are retiring the webhook connector, but webhooks will still be used in the workflow app... at least I hope so.
-
Nice. I'll give that a look when I have a chance.
-
fyi... here is the forum I found that has the correct format: community.atlassian.com/.../2749257
-
I only put the JSON code in Solarwinds Alert. I didn't put any code on the workflow side.
-
It's working great for us. The only issue is that the message sends as whoever created the workflow, so it has my name attached to every alert sent to Teams... imo, this is a flaw and should be fixed. I even have it configured to send as flow bot, but still sends as me. The only challenge was getting JSON in the correct…
-
I am not a JSON code expert by any means, in fact I know very little... but the examples they give on the power automate website do not work and I kept getting "NULL" errors for attachments and body. I finally found a forum online where someone had figured out the right format. I posted my adaptation below and it's working…
-
Yeah, I had to create a policy allowing our Solarwinds primary server to the specific URL on port 443 - example: "prod-35.westus.azure.com" or something like that.
-
I hope I'm understanding correctly and I can still use webhooks with the Workflows app, b/c I just spent 2 days getting this working. If so, here's how I set it up. Final product: Here's how I got there: - Right click your team or chat and select "Workflows" - Select "Post to a chat when a webhook request is received" -…
-
Thanks!
