time-conversion

[strowi]

Hi,

i am trying to get this working with status.hetzner.com to either add some annotations or get a list of events shown.
They provide rss/atom feeds, with dates like:

  <entry>
    <id>https://status.hetzner.com/2e715748-fddd-427b-a07b-b34a5a9edee3/0</id>
    <updated>2025-04-09T11:20:09+00:00</updated>
    <link href="https://status.hetzner.com/incident/2e715748-fddd-427b-a07b-b34a5a9edee3" />
    <title>Phishing emails stealing logins and credit card data</title>
    <category term="General"/>
    
  <content type="xhtml">
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p>Start: 2024-07-05T06:00:00+00:00</p>

(They also provide more detailed json, but i doubt the link "https://status.hetzner.com/_next/data/QProyRhlViKY54HDLI54L/en.json" will persist and ist probably generated).

I already do get some data and fields, but the time seems to be in the wrong format and i can't get it converted the right way.

Maybe someone else was luckier than me?

[gdiana]

I would advise to use the INFINITY JSONATA parsing feature and use the $MAP function to parse the date as I do.

{
"pageProps": {
"systems": [
{
"@id": "/systems/1",
"@type": "System",
"id": 1,
"systemState": "hidden",
"titleDe": "Allgemein",
"titleEn": "General",
"descriptionDe": "Allgemein",
"descriptionEn": "General",
"parent": null,
"children": [ ],
"createdAt": "2021-02-12T14:45:28+00:00",
"updatedAt": "2022-11-18T21:24:13+00:00",
"childIds": [ ]
},...

$map($.pageProps.systems,function($v){
{
"timeCreated" : $v.$fromMillis($toMillis(createdAt)),
"timeUpdated" : $v.$fromMillis($toMillis(updatedAt))

}
})

Here it is

and then use the Convert field type transformation to convert to time oin Grafana

with final result. You can set any date format you require using the transformation convert field type options

[strowi]

Thank you for that example @gdiana , it seems i wasn't that far off. I tried fiddling with the parsing-options a bit.

With this:

• url: https://status.hetzner.com/_next/data/QProyRhlViKY54HDLI54L/en.json
• $.pageProps.incidents.incidentHistory[*]

Which seems correct to me? But the annotations won't show up in the dashboard (eg. last status from date 2025-08-15; but nothing even for 30d range) .

[gdiana]

Ok, but what is it you trying to display on the dashboard and what panel are you trying to use?

Also what is the json path to the data you wish to display?

I used your example path and it worked fine, but had a lower path included in it?

There are incidents and incident updates?

[strowi]

Above screenshots are from the "create annotations" panel. They should show up on all panels, i didn't include that (thought it was trivial):

The json contains maintenance and incidents (from hetzner) that i would like to display as annotations in a panel/dashboard.
The format for times is the same, but it is nested differently as i found out (sorry about that).

As i understand, there should be an annotation for each element of $.pageProps.incidents.incidentHistory[*] (as detected in the screenshot) from time -> endTime with the appropriate data.

Or is the problem still that it is considered as string in startTime (string) i would expect "first value" to show an error then.

[gdiana]

Ok I was barking up the wrong tree.

I looked at the show annotations panel and they did not appear there either?

[strowi]

I added another panel of type "Annotations List" but they don't show up there either.

[gdiana]

Ok after a bit of fiddling I got it to "work"?

I will try full monty. I understand annotations may cover a range and looking at some it appears a first annoucement is made and there are also follow up announcments but they are at different levels but all may be handled by JSONATA but I am not sure what it is that you require?

The issue was with the JSONATA parsing and also as noted by GRAFANA the format to be used must be Data Frame

[gdiana]

Ok did some more and it appears to be working better now.

The problem is that incident History also contains at a lower level incident Updates

So if one wishes to display all events one will have to capture these sub event as well

To do this in JSONATA you will have to change the path to $.pageProps.incidents.incidentHistory.incidentUpdates and then use the %. to refer 1 level back up. Then one may create the entire and sub events as well.

It appears the need to use the "Data Frame" format was the issue

https://grafana.com/docs/plugins/yesoreyeram-infinity-datasource/latest/annotations/annotations/#:~:text=To%20add%20annotations%2C%20select%20the,%E2%80%9CData%20Frame%E2%80%9D%20as%20format.

I hope this helps/ed.

[strowi]

@gdiana Thank you very much, that really helped! ;)

For now i am going with this, it will at least allow the pop-up to show some more info. So at least we know sth. happened at hetzner which might need a closer look.

$map($.pageProps.incidents.incidentHistory, function($v){
{
  "time": $v.$toMillis(createdAt),
  "event": $v.titleEn,
  "description": $v.descriptionEn
}
})

And when i had some more time to really get familar with it try to apply the rest of your suggestion regarding the sub-level.

[gdiana]

Just for info this is what I last used

$map($.pageProps.incidents.incidentHistory,function($v){
{
"time " : $v.$toMillis(startTime),
"end time" : $v.$toMillis(endTime),
"event" : $v.titleEn,
"description" : $v.descriptionEn,
"tags" : $v.incidentState,
"id" : $v.uuid

}
})

I suggest you create 2 levels of annoations.

One at the higher level coloured in RED $.pageProps.incidents.incidentHistory
Call them INCIDENTS
and one at the lower level clouured BLUE $.pageProps.incidents.incidentHistory.incidentUpdates
and they should then overlay one another.

[gdiana]

Ok I tried this and it worked

This allows a mix and match of upper and lower levels from the history.

`$map($.pageProps.incidents.incidentHistory,function($v){
{
"time " : $v.incidentUpdates.$toMillis(createdAt),
"end time" : $v.incidentUpdates.$toMillis(updatedAt),
"title" : $v.titleEn,
"text" : $v.incidentUpdates.descriptionEn,
"tags" : $v.incidentUpdates.incidentState,
"id" : $v.uuid

}
})`

[strowi]

Nice, that looks much more useful now. Thx again! ;)