Skip to content
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.

trap handling in distributed mode #655

Closed
centreon opened this issue Aug 26, 2008 · 3 comments
Closed

trap handling in distributed mode #655

centreon opened this issue Aug 26, 2008 · 3 comments

Comments

@centreon
Copy link
Collaborator


Author Name: kmizole - (kmizole -)
Original Redmine Issue: 178, https://forge.centreon.com/issues/178

Original Assignee: Julien Mathis


The traps can’t be handled by any other servers than the central one in a distributed architecture. I think every poller should be able to handle traps.

@centreon
Copy link
Collaborator Author


Original Redmine Comment
Author Name: kmizole - (kmizole -)
Original Date: 2008-08-28T15:25:33Z


things that i thought off for this ticket :

on the poller we should have : snmptrapd, snmptt and the trapHandler

Maybe it could be a specific trapHandler that send results to the main trapHandler on the central server.

If it’s not a specific trapHandler, database access to centreon must be enabled from pollers, so we need more accounts (centreon@%) to access centreon DB.

@centreon
Copy link
Collaborator Author

centreon commented Apr 8, 2009


Original Redmine Comment
Author Name: Thomas – aka Jogarem - (Thomas – aka Jogarem -)
Original Date: 2009-04-08T16:34:30Z


Replying to kmizole:

> The traps can’t be handled by any other servers than the central one in a distributed architecture. I think every poller should be able to handle traps.

Yes this would be a major improvement!!
Regards
Thomas

@centreon
Copy link
Collaborator Author


Original Redmine Comment
Author Name: Julien Mathis (Julien Mathis)
Original Date: 2009-04-25T14:23:13Z


it's working but not documented :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants