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

Documentation on key concepts #253

Open
martialblog opened this issue Jul 24, 2024 · 7 comments
Open

Documentation on key concepts #253

martialblog opened this issue Jul 24, 2024 · 7 comments
Labels
doc Documentation related enhancement New feature or request

Comments

@martialblog
Copy link
Member

Hi,

I feel like the documentation is missing an introduction to the key concepts of Icinga Notifications.

The 01-About page should maybe introduce what we then see in the web interface

  • What is an Event
  • What is an Incident
  • What is an Event Rule and how does it work
  • What is a Contact, Group, Schedule
  • What is a Channel
  • and so on

The Event Rules in particular could use a detailed documentation.

If this is an issue for icinga-notifications-web, feel free to move the issue

Regards,
Markus

@nilmerg
Copy link
Member

nilmerg commented Jul 24, 2024

This is planned to be covered by a blog series.

@oxzi oxzi added enhancement New feature or request doc Documentation related labels Jul 24, 2024
@martialblog
Copy link
Member Author

Looking forward to the series.

However, I still think there's merit in having these key concepts in the documentation. First, I think it is good to have everything in one place and second, blog posts are usually not edited over time. So If we want to update/change/improve the documentation in these key concepts a blog post probably won't be updated.

@oxzi
Copy link
Member

oxzi commented Aug 13, 2024

I wrote some paragraphs last week, trying to both ease the initial steps while explaining some concepts on the way: https://icinga.com/blog/2024/08/07/getting-started-with-icinga-notifications/

However, imho this does not replace solid documentation.

@martialblog
Copy link
Member Author

I think it describes the key concepts very well and most of it could just be copied in a "key concepts" or the "about" section in the docs.

@theFeu
Copy link

theFeu commented Sep 11, 2024

I just had a chat with @julianbrost and we thought it might make sense to reuse parts of the blogpost in the docs.
The concepts are explained rather well there, and it would be a shame if they just drowned in the blog after a while :)

@jprusch
Copy link

jprusch commented Sep 11, 2024

Hopping in on this one...
I'm just evaluating notifications, great solution & I got it working with Mattermost sending a webhook request.
The most difficult part was finding out, what is supported on the JSON payload of a webhook channel. Some documentation on this topic would be great.
image

@jprusch
Copy link

jprusch commented Sep 11, 2024

Second topic would be the use of filters when creating an event rule.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Documentation related enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants