Hmm, can you tell me more about the dt.query dependency? I did suddenly start getting RCA results from my Problems alerts (although it just points to itself), but I didn’t understand why it worked. Now because of your comment I realize it was because I added a dt.query property to my Event properties event template.
From the Davis AI Semantic Dictionary docs, it states that dt.query is used for showing a graph in the Problem card, so that was the reason I had added it. It doesn’t mention anything about RCA being dependent on it.
What kind of query should we be putting there? Because my alert is a Records type analyzer, I tried building a query that would show me a graph of historical data in the Problem card, but I couldn’t figure out how to get the graph filtered down to the entity/entities being alerted on. I tried a query like this:
timeseries {
provisioned = max(purefa_volume_space_bytes, filter: {space == "total_provisioned"})
,virtual = max(purefa_volume_space_bytes, filter: {space == "virtual"})
}
,by: `dt.entity.purestorage:fa-volume`
,interval: 1m
,filter: {
`dt.entity.purestorage:fa-volume` == "{dt.entity.purestorage:fa-volume}"
}
| fieldsAdd host_used_pct = 100 * virtual[] / provisioned[]
My hope there was that the event property engine would replace the {dt.entity.purestorage:fa-volume} in the filter, but it doesn’t. I even tried replacing the dt.entity stuff with dt.smartscape to see if the graph would display properly in the new Problems app, but no, it doesn’t work. For some reason, it doesn’t resolve the {dt.entity.purestorage:fa-volume} (or the dt.smartscape version if I use that) to an actual ID.
What’s really weird is that if I have my by:{} clause setup like this:
,by:{dt.entity.purefa:volume}
It will resolve that to the volume entity ID unless I put ticks around it. But even without ticks, it doesn’t resolve it in the filter clause. It makes no sense…
But anyways, if I have the dt.entity/dt.smartscape filter in the dt.query, the query doesn’t work and I don’t get a graph (but I still get an RCA to the alerted-on volume returned).
I even tried removing the dt.entity/dt.smartscape filter in hopes that maybe the Problems engine would automatically add the filter to the alerted entity/entities into the query, but when I do that, it just shows every PureFA volume in our environment on the Problems graph…
Hmm, I just looked at the latest alerts and, even though I have a dt.query, the newer alerts aren’t generating an RCA anymore… I don’t know what else I changed, but now they aren’t generating an RCA and previously they were…
Anyways, yeah, i would like to learn more about this dt.query property, how it affects RCA, and how we are supposed to use it to generate a graph as stated in the Davis AI documentation.