I asked this 3-4 yrs ago. Not possible. One way you can kind of accomplish your goal is using json. This is how I keep track of TR-143 diag data.
As for why I’ve done it this way, the TR-069 spec only specifies the CPE has to send a 8 DIAGNOSTICS COMPLETE event. But no other information about what diagnostic event occurred. So before a diagnostic is requested of the CPE, I store a bit of data about what diagnostic action was requested (IPPing, upload speedtest, download speedtest, UDPEcho, DSL loop, wifi, etc), and sometimes extra information like in the case of DSL loop diagnostics, I need to know which line instance the diag was performed on. When the 8 DIAGNOSTICS COMPLETE event comes back, I spin through the items in the vparam and figure out which one has a status of ‘Requested’ then I know what data to capture, do a little pre-processing on it and then package up the data and send it to our subscriber management server.
I have a vparam called Diagnostics. Here is the data currently stored in it for one of our customers.
{
"Upload": {
"source": "CAF",
"timestamp": "2022-03-24T23:03:15-08:00",
"entityId": 2738775,
"completed": 1648191835327,
"status": "SUCCESS"
},
"Download": {
"source": "CAF",
"timestamp": "2022-03-24T23:04:14-08:00",
"entityId": 2738849,
"completed": 1648191890935,
"status": "SUCCESS"
},
"IPPing": {
"source": "Dashboard",
"timestamp": "2022-03-31T23:59:08-08:00",
"entityId": 7931473,
"completed": 1648799955061,
"status": "SUCCESS"
}
}