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

New button for external url #44

Closed
duylong opened this issue May 13, 2020 · 4 comments
Closed

New button for external url #44

duylong opened this issue May 13, 2020 · 4 comments
Labels
3.7 Version 3.7

Comments

@duylong
Copy link

duylong commented May 13, 2020

Hi,

What do you think of creating a new button in host's details with a drop-down list to external URLs that we would have defined in the conf?

external_urls: 1
external_url_lists:
  Thruk: https://www.example.com/thruk/#cgi-bin/extinfo.cgi?type=1&host={{HOSTNAME}}
  Other: ...
@nook24
Copy link
Member

nook24 commented May 19, 2020

Unfortunately most of the configuration is unknown to the Statusengine Interface, like IP addresses, contact configuration, check commands and so on.
Unlike Statusengine 2 which is a drop-in replacement for NDOUtils and has access to all of the Naemon configuration, Statusengine 3 was completely designed as a configuration less but fast status only database.

This is also the reason why it is more or less not possible to show the ip address of a host like you suggested in #41.

The idea is to have a separate configuration database that is used to generate the Naemon configuration and query Statusengin to get the current state of an object.

The question is, is it helpful for you to have one or more URLs for all hosts and services, where only hostname, service_description and status related information can be replaced dynamically?
If yes, this is not a big deal to implement.

But it will not be as dynamic as you may expect due to the lack of information.

With https://github.com/it-novum/openITCOCKPIT (the project of my employer) you can join the Statusengine database with a configuration database to get features like dynamic urls and many more:
Bildschirmfoto 2020-05-19 um 20 17 35

Maybe this could be interesting for you or maybe not

@duylong
Copy link
Author

duylong commented May 20, 2020

I had seen the openITCOCKPIT project but I didn't want to add another solution to my architecture. I want to keep it simple :)

Yes, having the hostname or service_description are sufficient, there is no need to have further in Statusengine 3. The goal is to have an identifier (common to all other external solutions), we don't need a persistent database.

Statusengine stores logs/metrics in a MySQL database, can't we enrich a Redis database to use it as a data cache for example?

nook24 added a commit that referenced this issue Feb 27, 2021
@nook24
Copy link
Member

nook24 commented Feb 27, 2021

Done :)

Bildschirmfoto 2021-02-27 um 14 09 27

#external_url_lists:
# - name: Ticketsystem
# url: https://issues.statusengine.org/index.php?hostname=$hostname$&servicename=$service_description$
# - name: CMDB
# url: https://assets.statusengine.org/index.php?hostname=$hostname$
# - name: Docs of Statusengine
# url: https://statusengine.org

@nook24
Copy link
Member

nook24 commented Feb 28, 2021

Implemented and released with version 3.7

@nook24 nook24 closed this as completed Feb 28, 2021
@nook24 nook24 added the 3.7 Version 3.7 label Feb 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.7 Version 3.7
Projects
None yet
Development

No branches or pull requests

2 participants