Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Hello community. I have a question for you, regarding the integration between Solarwinds and Pagerduty. When I trigger a disk alert from Solarwinds - for example - 90% usage on disk D: , then an event is generated in Pagerduty with its identifier.

Hello community.
I have a question for you, regarding the integration between Solarwinds and Pagerduty.

When I trigger a disk alert from Solarwinds - for example -
90% usage on disk , then an event is generated in Pagerduty with its identifier.

How can I generate a second event an hour later with the same identifier taking into account that the value has probably already increased?

My idea is to keep the information updated to have visibility of the disk growth but in Pagerduty in the "Summary" or Message field

Regards.

Find more posts tagged with

Accepted answers

All comments

mark.gover

You could always create a reset action to email when the issue is resolved?

ihigareda

Thanks Marca.
Currently we do not use email to send alerts, only Pagerduty, the main dashboard acts as a hub.

mark.gover

We use PD too but our SW system emails PD to notify users of the issue. When the issue resolves a reset action email is sent to PD.

ihigareda

I understand what you're telling me. I'm looking to implement this for a monitoring team that is 24x7, the flow is as follows:

- Trigger from solarwinds to pagerduty (greater than 90% last 10 minutes)
- In Pagerduty they validate the information and escalate with the teams, then mark the alert as acknowledged.

- At this point I'm looking for the possibility that the event created by the first alert at 90% can be updated a second time perhaps when it has already exceeded 93%.

Pagerduty

1st alert (90%) - marked as acknowledged
EVENT: 001
DATE: 10/29/24 - 09:00 am
Summary: The storage unit has 10% available, please send it to those responsible.

2nd alert (95%) - new ()
EVENT: 001 (related to the first event)
DATE: 10/30/24 - 11:00 am
Summary: The storage unit has 5% available, please send to those responsible.

Update in Title or summary.