Skip to main content

September 16, 2024

New features

New endpoint for returning alerts in the Computers API

The Computers API now offers a new endpoint that allows you to consult the alerts generated in the provider, facilitating the analysis and management of incidents, and helping to maintain control over the infrastructure.

  • Endpoint: GET /v1/alerts

The alert results can be filtered based on the following criteria ($filter parameter):

  • Customer (customerName): alerts generated on a specific customer (example: customerName eq 'customer 01').
  • Status (status): open, in process or closed alerts (example: status eq 'Dealing').
  • Open by period (openingDate): alerts open in a specific period (example: openingDate eq 2024-09-16T19:05:52.8781366Z).
  • Closed by period (closingDate): alerts closed in a specific period (example: closingDate eq 2024-09-16T23:00:45.8781366Z).
  • Computer (deviceName): alerts generated on a specific computer. (example: deviceName eq 'computer 01').
  • Criticality (criticality): light, moderate or critical alerts. (example: criticality eq 'Moderate').

The endpoint query returns detailed data on each alert that has been active since 09/16/2024:

  • Alert name
  • Criticality
  • Status
  • Opening date
  • Closing date
  • Classification
  • Opening time
  • Alert description
  • Device name
  • IP address
  • Manufacturer
  • Model
  • Serial number
  • Department
  • Unit
  • Customer
  • Site

For more information on this endpoint, access the API Reference.


Improvements

Contact information for the person responsible for the computer

In order to make it easier to manage computers by identifying the person responsible for each device, the following fields have been added to the register:

  • Name of person responsible
  • E-mail of person responsible
  • Phone of person responsible

These fields allow you to quickly identify and contact the person responsible for the computer whenever necessary.

The information can be entered/updated and consulted via the Computers API, using the following endpoints:

  • Query endpoint: GET /v1/computers
  • Update endpoint: PATCH /v1/computers/{computerId}