Timerange Impact to Query Execution
Each query specifies a timerange using SINCE and UNTIL blocks.
This timerange has an impact on the query execution and the returned data.
Topology Data
Topology data (entities, associations) are impacted in several ways by the timerange.
Entity Activity
Each entity has isActive boolean field defined and it is true for active entities.
Each query always returns entities or traverse over entities which were active
for at least sometime during the query timerange.
If isActive is fetched or used in filtering, ordering or grouping, then the value which is
used is the one valid at the end of the query timerange.
Attributes and tags are possibly mutable state of an entity. If they are fetched,
used in filtering, ordering or grouping, then the value which is used is the one
valid at the end of the query timerange. It is the same rule applied to
isActive field.
Associations
Associations can be used to traverse between entities in a query.
An association can be created or deleted over time. It means that the topology
in which the query traverses can evolve over time. The query traverses only over
those associations which are valid (exists) for at least some time
during the query timerange.
Metric Data
A query always returns metric data for the specified timerange. Both time series
or rolled up.
Events and Logs
Only events and logs with a timestamp in the query timerange
are returned or processed by the query execution.