Can support for service_status be added to PagerDuty ?

[eseyman]

I use the PagerDuty stream connector and I have been asked to filter out service checks that are in UNKNOWN status before sending them to PagerDuty.

I thought I could use the "service_status" parameter but it is not taken into account be the PagerDuty stream connector. Can support for this parameter (and "host_status") be added?

[lucie-tirand]

Hello :)

I have the impression that service_status and host_status are already managed by the SC PagerDuty according to the documentation: https://docs.centreon.com/fr/docs/24.04/integrations/event-management/sc-pagerduty-events/#standard-parameters

And that seems to be borne out by the content of the SC too : https://github.com/centreon/centreon-stream-connector-scripts/blob/develop/centreon-certified/pagerduty/pagerduty-events-apiv2.lua#L67

Or have I misunderstood your request?

[eseyman]

There are several parameters that easily mistaken for each other...

accepted_elements is a parameter that gives the list of broker elements used to filter events.
host_status and service_status are two other parameters that give list of accepted host and service statuses, acting like a second filter behind accepted_elements.

The pagerduty SC handles all three parameters : https://github.com/centreon/centreon-stream-connector-scripts/blob/develop/centreon-certified/servicenow/servicenow-incident-events-apiv2.lua#L68-L72

[lucie-tirand]

Hello :)

So from what I understand, the parameters host_status and service_status exist but are not taken into account when the stream connector is executed?

[eseyman]

the parameters host_status and service_status exist but are not taken into account when the stream connector is executed?

Correct.

[eseyman]

Okay, coming back to this after a long while, it appears that parameters for the PagerDuty module are not taken into account even after restarting the broker. It appears more steps are necessary (exporting the configuration to all pollers?).

Still investigating...

[tanguyvda]

Hello @eseyman

usually people have the stream connector configured in their central-broker-master configuration. Which means that the configuration is linked to the central server.

If that's the case, you just need to export the configuration on the central server. You can check if your configuration is fine using the following methods:

• after your configuration export on the central, the /var/log/centreon-broker/pagerduty-events.log should display the list of parameters that you have configured. Therefore, you should see the service_status paramater (which in your case should probably set to 0,1,2)
• if you're not seeing this parameter, then you need to check the broker configuration file. /etc/centreon-broker/central-broker.json. You should see inside this json structure the stream connector with the parameters that you have configured from the web interface

If that is not the case, then it means that you have an issue with the configuration export on your central server (which is quite unusual on a central server since the mechanism is very basic)

Let us know the result of those two checks

Regarding your pollers, you have nothing to do apart from the very first time you create the broker stream connector output. You need to restart the centengine process on every poller (central server included). It is needed for the central server to build a cache that is used by stream connectors

Have a nice day,
Regards