Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help for integration #1035

Open
FranB1989 opened this issue Apr 29, 2024 · 3 comments
Open

Help for integration #1035

FranB1989 opened this issue Apr 29, 2024 · 3 comments

Comments

@FranB1989
Copy link

Hi, sorry to disturb anyone, I know that this is not an issue but on my new work, my boss requests me that if I could use Nagstamon to connect to our own python + django rest api application.

The application that we have developed with python and DRF is a monitoring application with alerts and we need to Nagstamon has to be able to connect our application. To accomplish that I've thought to simulate that my python application is a Nagios, or a Zabbix, or some monitoring application that Nagstamon allows to connect.

Any idea that how could I do this?

I've thought to create an specific endpoint with basic authentication and serve to nagstamon the request that, I guess, it sends to different monitoring applications.

Thanks in advance

Fran

@HenriWahl
Copy link
Owner

@FranB1989 in the Servers directory you find all currently available and all individual servers.

@FranB1989
Copy link
Author

Hey Henri, thanks for the answer, I've used the check_mk connector to simulate that I'm a check_mk server.
Finally I've made a new endpoint on my application and I'm trying to develop all the logic that Check MK uses to comunicacte with Nagstamon.

For that I've could seen, Nagstamon makes some HTTP requests with some arguments to check mk and this respond with the values that check mk needs to show the alerts in this grid.

Thinking about of that, It is possible to show the "generic" server in the combo box of Nagstamon to use this generic server to connect?

Thanks!

@HenriWahl
Copy link
Owner

Well, as Nagstamon being started in 2008, once upon a time the generic server was just Nagios, being the grandfather of a lot of monitoring servers. So if you want to use generic access just use Nagios, but honestly this is the worst choice if you are able to design the API on your own. Most of Nagios' descendants chose to serve with an API, while Nagios still delivers pure HTML which Nagstamon scrapes and evaluates.

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

No branches or pull requests

2 participants