argus-server 2.5.0__tar.gz → 2.7.0__tar.gz

{argus_server-2.5.0 → argus_server-2.7.0}/.pre-commit-config.yaml

@@ -8,7 +8,7 @@ repos:
         exclude: &exclude_pattern '^changelog.d/'
     -   id: debug-statements
 -   repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.12.0
+    rev: v0.14.13
     hooks:
         # Run the linter
     -   id: ruff
@@ -20,4 +20,6 @@ repos:
     rev: v1.36.4
     hooks:
       - id: djlint-reformat-django
+        args: [--configuration, pyproject.toml]
       - id: djlint-django
+        args: [--configuration, pyproject.toml]

{argus_server-2.5.0 → argus_server-2.7.0}/CHANGELOG.md

@@ -8,6 +8,128 @@ This project uses [*towncrier*](https://towncrier.readthedocs.io/) and the chang
 
 <!-- towncrier release notes start -->
 
+## [2.7.0] - 2026-01-23
+
+This release improves the UX for creating planned maintenance tasks, by having
+dedicated pages for it and allowing all logged in users to see the list of
+future, ongoing and past planned maintenance periods. To take full advantage of
+thisi column, see NOTES.md.
+
+Furthermore, admins can create filters that can be used (but not edited) by
+everyone.
+
+The sorting of the incident list can now be controlled via relevant columns,
+but only one column at a time.
+
+There are lots and lots of new columns! See NOTES.md
+
+There are two new column presets, one for making notification filters and
+another for making planned maintenance tasks.
+
+A long-standing bug has been fixed that prevented the sending of notifications,
+see NOTES.md.
+
+### Added
+
+- Added searchable `id` column
+  ([#1288](https://github.com/Uninett/Argus/issues/1288))
+- Made it possible to filter on event types
+  ([#1455](https://github.com/Uninett/Argus/issues/1455))
+- Added column for marking incidents as under maintenance
+  ([#1589](https://github.com/Uninett/Argus/issues/1589))
+- Prohibited editing planned maintenance task closed for longer than 12 hours
+  ([#1648](https://github.com/Uninett/Argus/issues/1648))
+- Added pictures of each column type to docs
+  ([#1653](https://github.com/Uninett/Argus/issues/1653))
+- Save current incident filters as a user preference and restore on page load
+  ([#1682](https://github.com/Uninett/Argus/issues/1682))
+- Added a new column showing all tags of an incident.
+  ([#1698](https://github.com/Uninett/Argus/issues/1698))
+- Add new `end_time` and `narrow_end_time` columns to display the `end_time` of
+  an incident ([#1715](https://github.com/Uninett/Argus/issues/1715))
+- Add compact severity columns with filtering and sorting
+  ([#1717](https://github.com/Uninett/Argus/issues/1717))
+- Added management command to connect incidents to new planned maintenance
+  tasks ([#1734](https://github.com/Uninett/Argus/issues/1734))
+- Added first version of pages for CRUD-ing planned maintenance tasks. Everyone
+  can see them but only admins can alter anything
+  ([#1735](https://github.com/Uninett/Argus/issues/1735))
+- Added management command to remove incidents from ended planned maintenance
+  tasks ([#1736](https://github.com/Uninett/Argus/issues/1736))
+- Made it possible to mark a filter as "public". This means that anyone can use
+  it in the incident list, for notification profiles or for making planned
+  maintenance tasks. The flag can currently only be set via the admin
+  interface, and is thus limited to administrators.
+  ([#1742](https://github.com/Uninett/Argus/issues/1742))
+- Add sortable columns to incident table
+  ([#1980](https://github.com/Uninett/Argus/issues/1980))
+- Added a very rough and ready column to show an incident's events.
+- Added two new column presets:
+
+  * "notifications" with columns useful for making notification profiles
+  * "on maintenance" with columns useful for finding things that will be on
+    planned maintenance
+- Argus now supports Django 6.0
+
+### Changed
+
+- Implemented a Contributor License Agreement for Argus, based on the Free
+  Software Foundation's Fiduciary License Agreement
+  ([#956](https://github.com/Uninett/Argus/issues/956))
+- Replace column filter button with debounced auto-submit
+  ([#1575](https://github.com/Uninett/Argus/issues/1575))
+- Improve toast notification accessibility with ARIA attributes and screen
+  reader support ([#1711](https://github.com/Uninett/Argus/issues/1711))
+- Changed label of start time column to 'Start time'
+  ([#1718](https://github.com/Uninett/Argus/issues/1718))
+- Renamed column `start_time_and_age` to `narrow_start_time_and_age` and added
+  wider column named `start_time_and_age`
+  ([#1719](https://github.com/Uninett/Argus/issues/1719))
+- The buttons in the column layout preview were disabled.
+- The theme chooser on the user preferences page now shows the text color for
+  each color palette in addition to the background color.
+
+### Fixed
+
+- Added key requirements to error message in tag validation
+  ([#511](https://github.com/Uninett/Argus/issues/511))
+- Fixed dropdown multi-select fields (e.g. Source Types) selecting first item
+  when clicked ([#1697](https://github.com/Uninett/Argus/issues/1697))
+- Show meaningful error messages in UI and log full tracebacks for HTMX errors
+  instead of generic "500 Internal Server Error" and HTML content
+  ([#1702](https://github.com/Uninett/Argus/issues/1702))
+- Fixed page size preference being reset to default when visiting the incidents
+  page without a `page_size` URL parameter
+  ([#1704](https://github.com/Uninett/Argus/issues/1704))
+- Fix bug where multiselect is not cleared when de-selecting all options
+  ([#1751](https://github.com/Uninett/Argus/issues/1751))
+- Fixed longstanding bug that led to fewer notifications than expected. Instead
+  of checking when an *event* happened in order to decide whether to send
+  a notification, we only checked when the incident *started*. So, no
+  notifications could be sent for long-lasting incidents if they started
+  outside of all active timeslots.
+- Missing filters are now handled better. If a filter was deleted while it was
+  in use by the incident list page, the page would get stuck with a "500 Server
+  Error" until the filter was manually removed from the session.
+
+
+## [2.6.0] - 2026-01-06
+
+This is a tiny release to finish up what was started at the end of 2025.
+
+### Added
+
+- Add preview for incident table preferences
+  ([#1658](https://github.com/Uninett/Argus/issues/1658))
+
+### Fixed
+
+- Filter on source type in dashboard. The previous release made it work for
+  notifications but not in the incident list in the frontend.
+- Fix bug where the incident table overlaps filter dropdowns
+  ([#1669](https://github.com/Uninett/Argus/issues/1669))
+
+
 ## [2.5.0] - 2025-12-04
 
 The big new thing this time around is a way to prevent notifications from

{argus_server-2.5.0 → argus_server-2.7.0}/CONTRIBUTING.rst

@@ -54,3 +54,21 @@ Nuts and bolts
 
   * How to write a changelog, and when `(local copy) <./docs/development/howtos/changelog-entry.rst>`_, `RTD <https://argus-server.readthedocs.io/en/latest/development/howtos/changelog-entry.html>`_
   * What we want to see in a commit message `(local copy) <./docs/development/howtos/commit-messages.rst>`_, `RTD <https://argus-server.readthedocs.io/en/latest/development/howtos/commit-messages.html>`_
+
+Contributor License Agreement
+=============================
+
+To contribute code to Argus, you need to sign our contributor license
+agreement, based on The Free Software Foundation's `Fiduciary License
+Agreement 2.0 <https://fsfe.org/activities/ftf/fla.en.html>`_.
+
+We use `CLA assistant`_ to streamline the process. When you create a pull
+request against the Argus repository and have not previously signed our
+agreement, the assistant will automatically post a comment on your pull
+request with instructions on how to sign it digitally using your GitHub
+account.
+
+`The full agreement text can be read at the CLA Assistant site.
+<https://cla-assistant.io/Uninett/Argus>`_
+
+.. _CLA assistant: https://cla-assistant.io/

{argus_server-2.5.0 → argus_server-2.7.0}/NOTES.md

@@ -3,6 +3,65 @@
 This file documents changes to Argus that are relevant for operations,
 customizers and end-users.
 
+## [2.7.0] - 2026-01-23
+
+### Planned maintenance
+
+This release improves the UX for creating planned maintenance tasks, by having
+dedicated pages for it and allowing all logged in users to see the list of
+future, ongoing and past planned maintenance periods. There is also a new
+column `under_plannedmaintenance`. This column depends on two new management commands:
+
+- `check_started_maintenance`
+- `check_ended_maintenance`
+
+Both takes an argument `--minutes` which defaults to 5. These commands connects
+and disconnects incidents to a planned maintenance task if they fit the
+criteria set in the filter(s).
+
+The commands are designed to be run via cron or similar repetitive scheduler.
+
+### Public filters
+
+Filters can now be public. At the moment they can only be created by admins in
+the admin. The idea is to make it easy to have a little library of the most
+useful, most used or just default filters, allowing you to get started quicker.
+
+### New columns
+
+- `id` and `search_id`
+- `under_maintenance`
+- `end_time` and `narrow_end_time`
+- `narrow_start_time_and_age` is the old `start_time_and_age`, a new
+  `start_time_and_age` is wider.
+- `compact_level` and `compact_select_levels`, only showing the number.
+- `events`, to help with making filters for sending notifications
+
+### New column layouts
+
+There are two new column presets, one for making notification filters and
+another for making planned maintenance tasks. With the classic built-in layout
+that means there are always a minimum of three column layouts available.
+
+### Expect more notification sent
+
+A long-standing bug has been fixed that prevented the sending of notifications
+of events that happened if the start of the incident was not covered by
+a notification timeslot. This might mean more notifications! Please set the
+`event types` filter to only the types of events desired.
+
+## [2.6.0] - 2026-01-06
+
+This is a tiny release to finish up what was started at the end of 2025.
+
+The feature for having mutiple column presets for the incident list is now
+finished. Please make add issue if you have a column-type you would like
+added.
+
+Also, there were some bugs with the typeahead for the tag filter and the new
+source system type filter that was introduced in 2.4.0, the ones we know of
+have been fixed.
+
 ## [2.5.0] - 2025-12-04
 
 This release adds a new app, "argus.plannedmaintenance", which uses a new

{argus_server-2.5.0 → argus_server-2.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: argus-server
-Version: 2.5.0
+Version: 2.7.0
 Summary: Argus is an alert aggregator for monitoring systems
 Project-URL: Homepage, https://github.com/Uninett/Argus
 Author-email: Uninett Opensource <opensource@uninett.no>
@@ -8,6 +8,7 @@ License: GPL-3.0-or-later
 License-File: LICENSE
 Classifier: Framework :: Django
 Classifier: Framework :: Django :: 5.2
+Classifier: Framework :: Django :: 6.0
 Classifier: Intended Audience :: Information Technology
 Classifier: Intended Audience :: System Administrators
 Classifier: License :: OSI Approved :: GNU General Public License v3 or later (GPLv3+)
@@ -25,7 +26,7 @@ Requires-Dist: django-htmx
 Requires-Dist: django-phonenumber-field[phonenumberslite]
 Requires-Dist: django-rest-knox
 Requires-Dist: django-widget-tweaks==1.5.0
-Requires-Dist: django<6.0,>=5.2
+Requires-Dist: django<6.1,>=5.2.8
 Requires-Dist: djangorestframework>=3.14
 Requires-Dist: drf-rw-serializers>=1.1
 Requires-Dist: drf-spectacular>=0.17

{argus_server-2.5.0 → argus_server-2.7.0}/docs/customization/htmx-frontend.rst

@@ -127,7 +127,7 @@ given a ``str``, this key must be available in the
 ``argus.htmx.incidents.customization.BUILTIN_COLUMNS`` dictionary. For
 example::
 
-    from argus.htmx.incidents.customization import BUILTIN_COLUMNS, IncidentTableColumn
+    from argus.htmx.incident.columns import BUILTIN_COLUMNS, IncidentTableColumn
 
     INCIDENT_TABLE_COLUMN_LAYOUTS = {
         "default": [

{argus_server-2.5.0 → argus_server-2.7.0}/docs/development/howtos/customizing-filtering.rst

@@ -27,24 +27,29 @@ changed incidents.
 FilterWrapper
 -------------
 
-Base class, the important methods are ``incident_fits`` and ``event_fits``.
+Base class, the important methods are ``incident_fits``, ``event_fits`` and
+``filter_fits``. The latter two take a single event. ``filter_fits`` checks
+both ``event_fits`` and ``incident_fits``, in that order.
 
 FallbackFilterWrapper
 ---------------------
 
 Subclass of ``FilterWrapper``. Merges a filter with the filter in the setting
-``ARGUS_FALLBACK_FILTER``.
+:setting:`ARGUS_FALLBACK_FILTER`.
 
-ComplexFilterWrapper
---------------------
+PrecisionFilterWrapper
+----------------------
 
-OR's together multiple simple FilterWrappers, used by NotificationProfile.
+AND's together multiple simple filters, using ``FilterWrapper`` by default. Not
+used directly.
 
-ComplexFallbackFilterWrapper
-----------------------------
+Has the methods ``incident_fits`` and ``event_fits``, and ``filter_fits`` which
+takes an event and checks both ``event_fits`` and ``incident_fits``, in that
+order.
 
-Subclass of ``FilterWrapper``. Takes the setting ``ARGUS_FALLBACK_FILTER`` into
-account for each filter.
+``NotificationProfile`` has the subclass ``NotificationProfileFilterWrapper``,
+which combines a ``PrecisionFilterWrapper`` with a ``FallbackFilterWrapper``.
+It is thus affected by the setting :setting:`ARGUS_FALLBACK_FILTER`.
 
 ---------------------------------------
 Matching a filter to multiple incidents

argus_server-2.7.0/docs/development/howtos/htmx-frontend/column_for_specific_ack_group.rst

@@ -0,0 +1,51 @@
+==================================================
+How to make a column for an ack with a known group
+==================================================
+
+You need a new template for the cell, for instance containing::
+
+    {% load argus_htmx %}
+    {% if incident|is_acked_by:column.context.group %}X{% endif %}
+
+Our recommended filename for the template file is::
+
+    ``htmx/incident/cells/_incident_ack_by_group.html``
+
+It is *necessary* to use a specialized settings-file for this, since you
+need to both set where to look for the additional template, and to set
+up the actual column.
+
+Tell Argus where the template is
+================================
+
+There are two available methods to tell Argus where the template is. They can
+be combined, but then the template in the hardcoded directory name (option 2)
+always takes precedence.
+
+1. Add a Django app at the start of :setting:`INSTALLED_APPS` that has
+   a directory ``templates/`` that contains the new template file. You can use
+   the same app for any other overrides.
+2. Add a directory to the :setting:`DIRS` list in the :setting:`TEMPLATES`
+   setting, see `Django settings: TEMPLATES
+   <https://docs.djangoproject.com/en/5.2/ref/settings/#templates>`_ in the
+   official Django documentation. Templates here will override any template
+   from any app, provided the relative path matches.
+
+Set up the column
+=================
+
+You need to add the column to a column config::
+
+    INCIDENT_TABLE_COLUMN_LAYOUTS = {
+        "mylayout":[
+            ..
+            IncidentTableColumn(
+                "mygroup_ack",
+                "MYGROUP",
+                "htmx/incident/cells/_incident_ack_by_group.html",
+                context={"group": "MYGROUP"},
+            )
+            ..
+        ],
+        ..
+    }

argus_server-2.7.0/docs/development/howtos/htmx-frontend/column_for_specific_tag.rst

@@ -0,0 +1,19 @@
+=======================================
+How to make a column for a specific tag
+=======================================
+
+You can add the column to a named column config::
+
+    INCIDENT_TABLE_COLUMN_LAYOUTS = {
+        "mylayout": [
+            ..
+            IncidentTableColumn(
+                "mytag",
+                "MYTAG",
+                "htmx/incidents/cells/_incident_tag.html",
+                context={"tag": "MYTAG"},
+            )
+            ..
+        ]
+        ..
+    }

{argus_server-2.5.0 → argus_server-2.7.0}/docs/development/howtos/sonarqube.rst

@@ -16,4 +16,13 @@ python:S1192 - String literals should not be duplicated
 If it makes it more readable, for example if configuration is happening within the
 Python code, then we accept it with "This is better for readability".
 
+python:S2208 - Wildcard imports should not be used
+--------------------------------------------------
+
+This is okay in settings files. Mark as false positive with "Django standard
+practice for settings files". Notice that `sonarqube`_ ignores all ``#noqa``
+so "#noqa: `F401`_, `F403`_" won't help.
+
 .. _sonarqube: https://www.sonarsource.com/products/sonarcloud/
+.. _F401: https://www.flake8rules.com/rules/F401.html
+.. _F403: https://www.flake8rules.com/rules/F403.html

{argus_server-2.5.0 → argus_server-2.7.0}/docs/development/management-commands.rst

@@ -466,6 +466,31 @@ whether the user is a superuser (superuser) or not (nosuperuser). Superusers
 have by default access to the admin, but this can be turned off with
 ``--nostaff``.
 
+Planned maintenance handling
+============================
+Connect new planned maintenance tasks with their covered incidents
+------------------------------------------------------------------
+
+There is a command ``check_started_maintenance``. It takes an argument ``--minutes``
+(default 5 min) and will find all planned maintenance tasks that have started within
+the last x minutes. For each of these tasks it finds all open incidents that are
+covered by it and adds them to the ``incidents`` list of that task if it isn't already
+there.
+
+This field will be used to show in the dashboard which incidents are covered by an
+ongoing planned maintenance task.
+
+Remove covered incidents from recently closed planned maintenance tasks
+-----------------------------------------------------------------------
+
+There is a command ``check_ended_maintenance``. It takes an argument ``--minutes``
+(default 5 min) and will find all planned maintenance tasks that have ended within the
+last x minutes. For each of these tasks it clears the ``incidents`` field of that task.
+
+This field is be used to show in the dashboard which incidents are covered by an
+ongoing planned maintenance task. Since the task has ended these incidents are not
+covered by it anymore.
+
 Deprecated/overlapping commands
 ===============================