Based on a proposal from University of Michigan: There should be a way get (time series) metrics on how many incidents are opened/closed/acked in Argus over time.
An API client could easily be written to generate these numbers from the current API version, but with the current state of the API, it likely needs to fetch all the involved incidents, which involves a lot of transferring of unnecessary data.
To enable this, there should perhaps be an endpoint that produces just the number of matching incidents to a filter, rather than returning a list of all the matching incidents. Perhaps even some sort of time-series capability could be added to the endpoint to avoid the need to make a million calls to get a million data points.
This needs a design discussion in the team, though.
hmpf
commented
1 year ago
Based on a proposal from University of Michigan: There should be a way get (time series) metrics on how many incidents are opened/closed/acked in Argus over time.
An API client could easily be written to generate these numbers from the current API version, but with the current state of the API, it likely needs to fetch all the involved incidents, which involves a lot of transferring of unnecessary data.
To enable this, there should perhaps be an endpoint that produces just the number of matching incidents to a filter, rather than returning a list of all the matching incidents. Perhaps even some sort of time-series capability could be added to the endpoint to avoid the need to make a million calls to get a million data points.
This needs a design discussion in the team, though.