I have AWS managed Open Search cluster, and I'm trying to implement anomaly detection. I'm pretty new to all these tools. Today I stumbled with this:
Inside the "Live anomalies" chart I can see a red bar indicating some sort of anomaly for that time. But below inside the "Anomaly overwiew" box I see zero anomalies.
The first chart is for the last 600 minutes. The second chart if for the last 7 days. I don't understand why the "Anomaly overview" chart doesn't show the same anomaly as "Live anomalies" chart does.
Related
I'm trying to look for a visual with the following specifications:
Job usage timeline (bar graph like)
Jobs can be part of a group
When two or more jobs of the same group overlap (timestamp) they should be
displayed in the next line
Timestamps can be days, hours, minutes and seconds precise Tooltips (hover over QuickInfo)
Here are the ones I've tried so far and why they didn't work:
R-Script: hc_vistime - (Couldn't be displayed)
R-Script: gg_vistime - (No tooltips)
Gantt - (Timestamps could only be days exact)
Craydec Timelines - (Overlaps would not start new line)
Any suggestions? Thanks in advance!
its been a month since I started using Apache Superset. I have a graph that gives the accuracy of an event occuring on a given hour shown below.
The event occuring is a column named 'prediction' which is either 'Left' or 'Right'. Is there a way to colorize the bars according to the value in 'prediction' column. If the prediction is Left then red colored bar and green colored bar when Right etc. I have checked metadata but I am not sure how I can edit it. Is there a way to achieve this?
I was able to solve it by using the 'prediction' column in breakdown function few days ago. Thank you Kamal for providing an answer as well!
Sorry for the large image, but it's the best way to to convey what I'm struggling to understand.
This is a simple alert that should trigger when a lambda generates 10 or more errors within 1 hour. Should be very simple, basic stuff.
So why does this alarm go to ALARM-state when the metric doesn't cross the threshold as shown in the image (green boxes). The new(?) bar at the bottom is the state of the alarm.
All relevant settings should be in the screenshot, its just "sum of errors over 1 hour"
I could just adjust the threshold to account for this weirdness, but I'm guess this is not an AWS-error, but a failure to understand from my part. I want to understand.
I did find this text hidden under an information-icon: "The alarming datapoints can appear different to the metric line because of aggregation when displaying at a higher period or because of delayed data that arrived after the alarm was evaluated."
I guess that is the answer, but I still don't like that the visualization doesn't use the same logic as the alarm. Kind of defeats the purpose.
I am creating a line graph chart in CF 9.
My cfchart code is below:
<cfchart showborder="yes"
chartheight="500" chartwidth="1000"
yaxistitle="% Correct" xaxistitle="Month"
sortXAxis="yes"
xAxistype="Scale"
showxgridlines="yes"
scaleFrom="1"
scaleTo="110"
showLegend="yes"
tipStyle="mouseOver"
title="Data Entry Audit %">
</cfchart>
Along the X-axis will display the Month Numbers, but it is counting by 2s, instead of 1,2,3,4,5,6 etc.. It is diplaying 0,2,4,6,8. There is data for month of January, so "1", but the 1 does not show up along the x-axis. I tried adding Scalemin=1 and ScaleMax=12, but it seems this is not supported with CF 9. Any help is much appreciated.
Thanks!
How many months are you displaying along the x-axis? Webcharts3D (the underlying charting tool) does a lot of automatic adjustments to ensure the best fit of chart elements. If Webcharts3D is skipping labels, then it may have decided there are too many to reasonably fit on along the axis. So it opts to display every other label instead.
I do not think cfchart has an attribute for overriding those particular settings on the x-axis. However, you can use the webcharts3d utility to customize/override the default settings. Specifically, play around with the xAxis settings in the "basic" tab (type, scale min/max, etcetera).
I am looking for a program that can make burndown charts which does not
assume that just because a day passes by, all work time for that day
automatically is assumed to have turned into progress for the current
sprint. I am thus not particularly interested in finishing a sprint at
some specific date, however I am interested in keeping track of if the
estimate is accurate.
I am only intending to use this for private programming (and
non-programming) projects, so it does not have to be a full fledged
scrum team solution (although I assume it would be).
To better explain what I am looking for, let's imagine I have a project
"Paint my house" with a single sprint consisting of nine tasks:
Buy paint, brushes and cleaning liquid.
Wash the North wall.
Wash the West wall.
Wash the South wall.
Wash the East wall.
Paint the North wall.
Paint the West wall.
Paint the South wall.
Paint the East wall.
Since this will be done in my spare time, at any day I might down-prioritize
this and do other stuff. And the painting is highly dependent
on the weather as well. Therefore a calender day passing does in
absolutely no way imply that the project will make progress for that day.
Every single application that I have found that can make burndown charts
fails utterly to fit this scenario. They all assume "calender time
passing equals progress". I want to supply the expected progress manually.
Any suggestions for a tool that is able to handle a project in this way?
(Related questions, but which does not provide me with an answer to my question.
https://stackoverflow.com/questions/829497/agile-methods-specifically-taylored-to-working-solo,
How have you implemented SCRUM for working alone?,
Using Scrum on a "Personal Time" Project)
Every single application that I have found that can make burndown charts fails utterly to fit this scenario.
That's because the whole point of a burndown chart is to predict when the sprint will finish, and to know whether you're on schedule or not. If you cannot paint because it rains, then you cannot make progress and you're then behind schedule, as the burndown chart will show. But if you make time a variable, then you have no schedule -- progress becomes independent of time -- and the trendline is completely unpredictable. So there's no point of having a burndown chart if the progression of time is unknown.
I think you are looking for something like kanban instead of scrum.
Here's an example of a chart in kanban.
http://www.targetprocess.com/blog/2010/02/cumulative-flow-chart-in-kanban-real-usage-example.html
HTH (6 months later)