Nagios Stackstorm integration #6113

MaheshSankaran · 2024-01-12T15:36:23Z

MaheshSankaran
Jan 12, 2024

Hi Team,
I am working nagios and stackstorm integration.
I have used kubernetes to deploy stackstorm.
I have installed nagios pack and
getting invalid endpoints when i test with st2service_handler.py like below,

python3 st2service_handler.py st2service_handler.yaml 1 testing CRITICAL 1 HARD 1 my_super_cool_router --verbose
Contents of config file: {'st2_api_key': 'Njk1OTVjNjIzMDhiZmE2NzZlNWQzMD****ZGMzODg2MjBhNjYxN2Q3MDYwZGE0YzVjNTEyNDk0YTM0NA', 'st2_username': 'st2admin', 'st2_password': '********', 'st2_api_base_url': 'http://10.182.0.45:32349/api/v1/', 'st2_auth_base_url': 'http://10.182.0.4:31182/auth/v1/', 'unauthed': False, 'ssl_verify': False}
Unauthed? : False
API key auth?: True
SSL Verify? : False

Checking if trigger "nagios.service_state_change" registered with st2.
Will GET from URL http://10.182.0.45:32349/api/v1/triggertypes/nagios.service_state_change for detecting trigger nagios.service_state_change.

Request headers: {'St2-Api-Key': 'Njk1OTVjNjIzMDhiZmE2NzZlNWQzMD******ZGMzODg2MjBhNjYxN2Q3MDYwZGE0YzVjNTEyNDk0YTM0NA'}

POST to URL http://10.182.0.45:32349/api/v1/triggertypes for registering trigger. Body = {'name': 'service_state_change', 'pack': 'nagios', 'description': 'Trigger type for nagios event handler.'}, headers = {'St2-Api-Key': 'Njk1OTVjNjIzMDhiZmE2NzZlNWQzMDgxMjRhNTA0ZGMzODg2MjBhNjYxN2Q3MDYwZGE0YzVjNTEyNDk0YTM0NA', 'Content-Type': 'application/json; charset=utf-8'}.

Traceback (most recent call last):
  File "/root/st2service_handler.py", line 183, in _register_trigger_with_st2
    _create_trigger_type(verbose=verbose)
  File "/root/st2service_handler.py", line 95, in _create_trigger_type
    raise Exception(msg)
Exception: Got response 404. Invalid triggers endpoint http://10.182.0.45:32349/api/v1/triggertypes.Check configuration!
Traceback (most recent call last):
  File "/root/st2service_handler.py", line 183, in _register_trigger_with_st2
    _create_trigger_type(verbose=verbose)
  File "/root/st2service_handler.py", line 95, in _create_trigger_type
    raise Exception(msg)
Exception: Got response 404. Invalid triggers endpoint http://10.182.0.45:32349/api/v1/triggertypes.Check configuration!

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/st2service_handler.py", line 160, in _register_with_st2
    _register_trigger_with_st2(verbose=verbose)
  File "/root/st2service_handler.py", line 190, in _register_trigger_with_st2
    raise Exception('Unable to connect to st2 endpoint {0}.\n'
Exception: Unable to connect to st2 endpoint http://10.182.0.45:32349/api/v1/triggertypes/nagios.service_state_change.

Failed registering with st2. Won't post event.

Am able to list trigger type,

k -n stackstorm exec -it stackstorm-st2client-5d6ddcf4b-nzdm4 -- st2 trigger list
Defaulted container "st2client" out of: st2client, generate-st2client-config (init)
+--------------------------------------+--------+--------------------------------------------------------------------------------------+
| ref                                  | pack   | description                                                                          |
+--------------------------------------+--------+--------------------------------------------------------------------------------------+
| core.st2.CronTimer                   | core   | Triggers whenever current time matches the specified time constaints like a UNIX     |
|                                      |        | cron scheduler.                                                                      |
| core.st2.DateTimer                   | core   | Triggers exactly once when the current time matches the specified time. e.g.         |
|                                      |        | timezone:UTC date:2014-12-31 23:59:59.                                               |
| core.st2.IntervalTimer               | core   | Triggers on specified intervals. e.g. every 30s, 1week etc.                          |
| core.st2.action.file_written         | core   | Trigger encapsulating action file being written on disk.                             |
| core.st2.generic.actiontrigger       | core   | Trigger encapsulating the completion of an action execution.                         |
| core.st2.generic.inquiry             | core   | Trigger indicating a new "inquiry" has entered "pending" status                      |
| core.st2.generic.notifytrigger       | core   | Notification trigger.                                                                |
| core.st2.key_value_pair.create       | core   | Trigger encapsulating datastore item creation.                                       |
| core.st2.key_value_pair.delete       | core   | Trigger encapsulating datastore item deletion.                                       |
| core.st2.key_value_pair.update       | core   | Trigger encapsulating datastore set action.                                          |
| core.st2.key_value_pair.value_change | core   | Trigger encapsulating a change of datastore item value.                              |
| core.st2.sensor.process_exit         | core   | Trigger indicating sensor process is stopped.                                        |
| core.st2.sensor.process_spawn        | core   | Trigger indicating sensor process is started up.                                     |
| core.st2.webhook                     | core   | Trigger type for registering webhooks that can consume arbitrary payload.            |
| linux.file_watch.line                | linux  | Trigger which indicates a new line has been detected                                 |
**| nagios.service_state_change          | nagios | Trigger type for nagios service state change event.**

cat service_state_change.yaml
---
name: service_state_change
pack: nagios
description: 'Trigger type for nagios service state change event.'

Please let me know what could be reason for this issue.

Thanks.

Answered by MaheshSankaran

Jan 15, 2024

Fixed it, Problem is with endpoint URL.
Thanks

View full answer

MaheshSankaran · 2024-01-15T15:47:47Z

MaheshSankaran
Jan 15, 2024
Author

Fixed it, Problem is with endpoint URL.
Thanks

8000

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Nagios Stackstorm integration #6113

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 1 comment

{{title}}

Select a reply

Nagios Stackstorm integration #6113

MaheshSankaran Jan 12, 2024

Replies: 1 comment

MaheshSankaran Jan 15, 2024 Author

MaheshSankaran
Jan 12, 2024

MaheshSankaran
Jan 15, 2024
Author