Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: support for Lookout for Equipment (L4E) complex data types #219

Closed
taleena opened this issue Sep 19, 2023 · 1 comment
Closed

Comments

@taleena
Copy link
Collaborator

taleena commented Sep 19, 2023

Discussed in https://github.com/grafana/iot-sitewise-datasource/discussions/217

Originally posted by diehbria September 13, 2023
This is a request to introduce support for L4E support into the Grafana SIteWise plugin. A high level explanation of L4E (lookout for equipment) can be found in this amazon blog post.

Users of SiteWise that also utilize L4E would like to be able to view and understand the anomolies detected by L4E within their grafana dashboards with the SiteWise Plugin.

L4E information in SiteWise is stored as a structured string, which is refered to as a "complex data type". Below is the expected structure for the L4E complex data type:

        value: {
          stringValue: `{"anomalyScore": ${anomalyScore} }`,
        },

an asset property which represents the L4E anomoly score may be identified through the dataSpecType as follows:

assetProperty.dataTypeSpec === 'AWS/ANOMALY_LOOKOUT_METRICS_RESULT' // if this is true, the asset property represents L4E anomaly data

High level use cases:

  • users should be able to easily identify which of their asset properties represent anomaly scores
  • users should be able to visualize the anomoly scores on their dashboard

Below is an example of how a user may want to be able to explore their anomoly scores:
Screenshot 2023-09-13 at 8 46 49 PM

In this example, the chart visualizes the periods in time with anomalies. An anomaly score of 1 is interpreted as an anomoly has occured at the given point in time. An anomoly score of 0 is interpreted as no anomaly is associated with the given point in time.

@iwysiu
Copy link
Contributor

iwysiu commented Aug 23, 2024

finished in linked pr

@iwysiu iwysiu closed this as completed Aug 23, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in AWS Datasources Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

4 participants