Salesforce notifier
This section describes the alerts for the Salesforce notifier service.
SfNotifierDown
Severity |
Critical |
|---|
Summary |
The sf-notifier service is down for 2 minutes. |
|---|
Raise condition |
absent(sf_auth_ok) == 1
|
|---|
Description |
Rasies when the Docker container with the sf-notifier service is
down for 2 minutes. In this case, notifications to Salesforce cannot be
sent. |
|---|
Troubleshooting |
Inspect the Salesforce notifier service logs using
docker service logs monitoring_sf_notifier. Since the issue may be connected to Docker or system, inspect the
Docker and system alerts.
|
|---|
Tuning |
Not required |
|---|
SfNotifierAuthFailure
Severity |
Critical |
|---|
Summary |
The sf-notifier service fails to authenticate to Salesforce for 2
minutes. |
|---|
Raise condition |
sf_auth_ok == 0
|
|---|
Description |
Raises when the sf-notifier service fails to authenticate to
Salesforce. In this case, notifications to Salesforce cannot be
sent. The alert fires after 2 minutes. |
|---|
Troubleshooting |
Verify the authentication credentials. Verify that the instance type is sandbox. Update the cluster model parameters and
redeploy the sf-container:
On the cluster level of the Reclass model,
update the cluster model parameters as required,
paying attention to sandbox and password. Refresh Salt:
salt '*' saltutil.refresh_pillar
Redeploy the sf-notifier container:
salt -C 'I@promethes:server and I@docker:server' state.sls docker
|
|---|
Tuning |
Not required |
|---|
SfNotifierErrorsWarning
Removed starting from the MCP 2019.2.2 update
Severity |
Warning |
|---|
Summary |
An average of {{ $value }} sf-notifier error requests appear
for 2 minutes. |
|---|
Raise condition |
increase(sf_error_count_total[2m]) > 0
|
|---|
Description |
Raises when the number of Salesforce notifier errors started increasing
over the last 2 minutes, indicating an issue with sending of the alert
notifications to Salesforce. The issue is typically connected with the
limits set in the Salesforce instance. The alert fires after 2 minutes.
Warning
The alert has been removed starting from the 2019.2.2
maintenance update. For the existing MCP deployments, disable this
alert.
|
|---|
Troubleshooting |
Inspect the sf-notifier service logs in
/srv/volumes/local/sf_notifier/logs/sfnotifier.log on the mon
node that runs the service container. If the logs contain many entries
with Salesforce exceptions, the issue can be connected with Salesforce
instance limits or the account used by sf-notifier. |
|---|
Tuning |
Disable the alert as described in Manage alerts. |
|---|