You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
first of all, big thanks for your plugin - that's execaly what I was looking for!I'm using Status History panel, but it doesn't work well as it was not connecting bar for time with no data.
I'm pinging our AWS inftrastructure every 15mins and saving metric only if an EC2 instance runs with a value running.
Since there exists just running state I don't have data when the instance was stopped or terminated. And that's my issue.
For instances which were running in the past, it shows them as running even it was stopped in the beginning of the period.
Please see attached image - there was just one instance which was really running (the middle bar)
Would it be possible to some kind of an extra option - a value is not present/null in at the start of period respect that?
Otherwise I'd need to save all other statuses, which I don't want to do unnecesary data in InfluxDB.
Many thanks,
The text was updated successfully, but these errors were encountered:
Since you don't have values in InfluxDB, you can ask it to fill the null values with for example the static value not running. Then these missing values are generated only while outputting the data, but the panel does see the data.
And since the screenshot loaded delayed for me, I only noticed now that you're using flux, so a simple |> fill(value: "not running") should be all you need
Hi,
first of all, big thanks for your plugin - that's execaly what I was looking for!I'm using Status History panel, but it doesn't work well as it was not connecting bar for time with no data.
I'm pinging our AWS inftrastructure every 15mins and saving metric only if an EC2 instance runs with a value
running
.Since there exists just
running
state I don't have data when the instance wasstopped
orterminated
. And that's my issue.For instances which were running in the past, it shows them as
running
even it was stopped in the beginning of the period.Please see attached image - there was just one instance which was really running (the middle bar)
Would it be possible to some kind of an extra option - a value is not present/null in at the start of period respect that?
Otherwise I'd need to save all other statuses, which I don't want to do unnecesary data in InfluxDB.
Many thanks,
The text was updated successfully, but these errors were encountered: