Bug 47697 – UNIVENTION_REPLICATION should consider a running UCS@school import

Bug 47697 - UNIVENTION_REPLICATION should consider a running UCS@school import


Summary:	UNIVENTION_REPLICATION should consider a running UCS@school import

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Monitoring (Prometheus or Nagios)
Version:	UCS 4.3
Hardware:	Other Windows NT

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-08-29 14:18 CEST by Michael Grandjean
Modified:	2021-05-14 16:34 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Grandjean

2018-08-29 14:18:46 CEST

A UCS@school import stops the Notifier for the duration of the import. In real world imports, they take long enough for "UNIVENTION_REPLICATION" to fire a "CRITICAL". 

With the HTTP-API-Import, we can delegate the import, e.g. to schools. In this case, every import of every school will trigger a CRITICAL alert in Nagios. 
This also means, that the people doing the import and those responsible for the monitoring are completey different teams.

It would be great, if UNIVENTION_REPLICATION could at least check on the UCS Master if a UCS@school import is running take that into account.

Comment 1 Ingo Steuwer

2021-05-14 13:56:05 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.