0.75

0.75 (2021-04-29)

This release adds a few more options to modem alarms.

ModemAlarmService

• Fixed the index for InactivityCheck.maximum.
• Added formatting option to error message templates:
  • Added the option to round numeric values: {actual:.3f}
  • Added the option to always sign numeric values (when rounded): {actual:+.3f}
  • This is applied to numeric fields and fields that can be numeric, like {actual} and {expected}.

0.74.4

0.74.4 (2021-04-22)

Small convenience hotfix for the ModemHealthCount.

ModemService

• [B] Changed ModemHealthCount.Response to group tag health counts instead of having them all in a big list.

Backwards incompatible changes

• [B] Changed ModemHealthCount.Response to group tag health counts instead of having them all in a big list.

0.74

0.74 (2021-04-15)

Changes

NamedLocationService

• Added NamedLocationService to save locations with a name. These location can then be used in other
  places, like alarms.
  A named locations can be either a Location, Area or Shape.
  • Added permission LOCATIONS_MANAGE to OrganizationPermission to manage named locations.

ModemAlarmService

• Added named to LocationCheck to use a named location for the check.

EventService

• ModemAlarmEvent title is now just the error message, without any additional data.
  The description contains the additional data, as before.

0.73

0.73 (2021-04-12)

Changes

ModemService

• Added ModemHealthCount to efficiently count how many of your modems per health level.
  Optionally, the counts can also be done per tag, specified by a TagSelection.

ModemAlarmService

• Added DelayCheck to trigger the alarm when message delay
  (the difference between sentAt and receivedAt) exceeds a given threshold.

0.72

0.72 (2021-03-25)

Mainly a bugfix releasese

Changes

• Bugfix in modem listing where in a specific edge-case modems would be un-listable after transfer.
• TLE update status does not affect server health any-more (causing restarts when outdated)

0.71

0.71 (2021-03-16)

The main focus for this release is tweaking the concepts previously introduced around alarms and health.
It also introduces the notion of features for organisations.
Features can be en- or disabled on a per-organisation basis
and have an effect on the set of features that organisations can use.

Changes

Organisation features

This change introduces 2 new feature (sets)

• HIBER: (All) the features as currently available under Mission Control
• HILO: Allows access to a separate dashboard that represents the
  HiberHilo product.

Health

• Modem selection (now) possible by custom health level names
• Health can now have multiple (named) colours associated with it.

Alarm

• A modem alarm now has a default health, which overrides the standard of "most severe".
• Allow the alarm to cause a health level for the modem even after a new message has come in.

0.69

0.69 (2021-03-04)

This release build on the new health levels by implementing them for alarm events, and replacing the deprecated health
implementation with the new health levels in a backwards-compatible way.
Additionally, this release introduces some new options to alarm checks, including a new check type for modem inactivity.

Changes

ModemService

• Replaced the deprecated health implementation with the new health levels. The default health levels are identical
  to the deprecated levels, so unless you change the health levels for your organization, this change is fully backwards
  compatible.
• Added Modem.inactivity with the time since the last message.
• Fixed a bug where stale detection would not be triggered.

ModemAlarmService

• Added a new check type: Inactivity.
  This check triggers when a modem is inactive for the configured period.
  This is similar to Modem.maximum_inactivity, but uses the alarms to add more flexibility, like the option to add
  multiple checks for multiple levels of inactivity and configuring the resulting health for each of those.
• Added a few options to the delta check:
  • encrypted: whether the individual field data should be encrypted (all messages are already encrypted).
    Encrypting the individual field values is (relatively) computationally expensive and may lead to
    a slightly delayed alarm event. In the future, some delta features may only
    be available to unencrypted values due to performance issues.
  • ignore_previous_value_not_found: Whether to ignore this check if the previous value is not found
    (i.e. there is no history).
• Added ModemAlarmEvent.health_level so the configured health is actually reflected in the event.

StatusService

• Deprecated ModemStatus.health. The status call will be update with health levels in a later release.

0.68

0.68 (2021-02-15)

Changes

EventService

• Added ModemStaleEvent.maximum_inactivity to allow maximum inactivity period of any length.
  • Deprecated ModemStaleEvent.maximum_inactivity_period, which allows maximum inactivity period in days only.
  • Updated modem-stale.json to reflect this added field.

HealthService

• Added HealthSelection to filter health levels.
• Added ListHealthLevels.Response.request to return the request, in case the selection was corrected.

ModemService

• Added Modem.maximum_inactivity to allow maximum inactivity period of any length.
  • Deprecated Modem.maximum_inactivity_period, which allows maximum inactivity period in days only.

ModemAlarmService

• Added a comment related to the processing of health levels from parent organizations.
• Fixes a bug where health level was not saved on modem alarms.
  (Note that health is not yet processed to the alarm event or modem health, this will be added soon.)

0.67

0.67 (2021-02-04)

This release introduces the concepts of health levels.
Over the next few releases, health levels will replace the static health we have now (for example for modems).

Health levels can be customized to as many as you need for your operations, for example:

• INTERVENTION
• DEFECT
• BATTERY
• HIGH
• LOW

The health level caused / produced by events and alarms can be customized in the next few releases.

Changes

• Added a new permission HEALTH_MANAGE to manage health levels.

HealthService

• Introduced the HealthService to manage custom health levels. See the proto file for more details.

ModemService

• Deprecated the static health on modem and added the new health levels.
  By default, the health levels are identical to the static health levels: OK, WARNING, ERROR.

  • Deprecated Modem.health.
    It will be implemented in terms of health levels in the future, as long as your health levels are identical
    to the static health.

  • Added Modem.health_level to show the modem's health as a HealthLevel.

  • Renamed Modem.HealthConfig.health_warning_period to health_unresolvable_period,
    since health is now customizable.

0.66

0.66 (2021-01-28)

Removed some deprecated code.

Changes

DashboardService

• [B] removed deprecated field selection from DashboardRequest.
• [B] removed deprecated fields satellites, ground_stations and map_blocks from DashboardRequest.Response.