Closed phalbert closed 2 months ago
A few other improvements I could make. cc @PeyGis , @Tankilevitch
Dashboard and Query Data: Implement a caching mechanism to store fetched dashboard definitions and query results for a certain duration.
Time Window: Allow users to configure the time window (currently hardcoded to 10 minutes) for the check_metric_data_exists
function. This gives users more control over the metric availability checks.
I think the implementation is too specific for the user use-case.
We have multiple resources touched to support that capability. And I think they needs to be separated.
Service
Host
Dashboard
Dashboard-Metrics
IMO we need to approach it by taking advantage of port builder capabilities, relations, mirrors, aggregation properties.
Service -> Dashboard Metrics or Service -> Dashboard -> Metrics Or Metrics -> Service
This change now adds available metrics as relational array of metric ids that are available for a host or service
Description
metric
andserviceMetric
to get specified metricsType of change
Please leave one option from the following and delete the rest:
Screenshots
API Documentation
Provide links to the API documentation used for this integration.