Summary

Status Values are populated in the timeline without considering the timestamps. When the values are populated regularly for each hour then the widget works fine. But if there are no values for few hours then the status is shown in a wrong timestamp/hour.

Description

We are using Status Timeline widget to show the result of Synthetic Monitors which are running once in 6 hours. Ideally, in the Status Timeline widget it should show the values for 0:00 timestamp and 06:00 timestamp, but we are seeing the values for 00:00 and 01:00. Without considering the timestamp, the status values are getting populated.

Steps to Reproduce

1. Create some sample Synthetic monitors which run once in 6 hours.
2. Use the following query in Status Timeline widget to fetch the result of the monitors.
   From SyntheticCheck select latest(result) facet monitorName,hourOf(timestamp) ORDER BY timestamp WITH TIMEZONE 'Australia/Brisbane' LIMIT MAX

Expected Behaviour

Ideally, the status timeline widget should show the values of status at the 0th hour and then at the 6th hour.

But it is showing the values at 0th hour and 1st hour. Without considering timestamp, status values are being filled in the cells.

Relevant Logs / Console output

Description

Status Table Widget - 0s show as nulls. Example:

Steps to Reproduce

Deploy Status Table widget - Run query with 0 result returned

Expected Behaviour

Literal 0 displayed, not null.

Description

I have created a widget using the NRQL status widget option, one of the configurations of this widget is to polling data every 5 seconds and everything is working if the time picker of the dashboard I have attached the widget to, stay with the default option but as long as I change the time picker option to any other value, the data stop the updating process and if you check the network tab under the inspector you will see that the request is happening but the value is not being re-render in the UI.

Steps to Reproduce

Add Data option -> Look into App & Visualisations -> enable the app Status Widget Pack -> select the option NRQL status Widget -> create a query like SELECT count(*) FROM Transaction -> set some critical and warning thresholds -> set polling to 5 seconds -> save the widget into a dashboard -> open the dashboard and see that the widget is being updating with the values every second in the default option of the time picker -> change dashboard's time picker to 5 minutes -> widget stop the re-render process of the value.

Expected Behaviour

Change the dashboard's time picker without affecting the re-render process of the widget's value since the polling should keeps happening every 5 seconds

Relevant Logs / Console output

Your Environment

• Browser name and version: Google Chrome Version 121.0.6167.139 (Official Build) (arm64)
• Operating System and version: macOS Sonoma 14.3

Repolinter Report

🤖This issue was automatically generated by repolinter-action, developed by the Open Source and Developer Advocacy team at New Relic. This issue will be automatically updated or closed when changes are pushed. If you have any problems with this tool, please feel free to open a GitHub issue or give us a ping in #help-opensource.

This Repolinter run generated the following results:

• Fail
  • ❌ readme-starts-with-nr1-catalog-header
  • ❌ code-of-conduct-should-not-exist-here
  • ❌ package-scripts-present
• Passed
  • ✅ license-file-exists
  • ✅ readme-file-exists
  • ✅ readme-contains-security-section
  • ✅ readme-contains-link-to-security-policy
  • ✅ readme-contains-discuss-topic
  • ✅ third-party-notices-file-exists
  • ✅ github-actions-workflow-file-exists
  • ✅ nr1-catalog-config-file-exists
  • ✅ nr1-catalog-screenshots-directory-exists
  • ✅ nr1-catalog-documentation-file-exists

Fail #

❌ readme-starts-with-nr1-catalog-header #

The README of a community plus project should have a NR1 Catalog header at the start of the README. If you already have a NR1 Catalog header and this rule is failing, your header may be out of date, and you should update your header with the suggested one below. For more information please visit https://opensource.newrelic.com/oss-category/. Below is a list of files or patterns that failed:

• README.md: The first 1 lines do not contain the pattern(s): Open source NR1 Catalog header (see https://opensource.newrelic.com/oss-category).
  • 🔨 Suggested Fix: prepend [![New Relic One Catalog Project header](https://github.com/newrelic/opensource-website/raw/master/src/images/categories/New_Relic_One_Catalog_Project.png)](https://opensource.newrelic.com/oss-category/#new-relic-one-catalog-project) to file

❌ code-of-conduct-should-not-exist-here #

New Relic has moved the CODE_OF_CONDUCT file to a centralized location where it is referenced automatically by every repository in the New Relic organization. Because of this change, any other CODE_OF_CONDUCT file in a repository is now redundant and should be removed. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view. Found files. Below is a list of files or patterns that failed:

• CODE_OF_CONDUCT.md
  • 🔨 Suggested Fix: Remove file

❌ package-scripts-present #

An eslint-check and eslint-fix npm script not found in file (package.json). NPM scripts for ESLint (eslint-check and eslint-fix) are required to properly integrate with the nerdpack system.

Passed #

NRQL querying metrics returns null / Oops Error in the widget.
NRQL itself works fine fine in other dashboard widgets and returns a value.

eg.1 FROM Metric SELECT clamp_max(count(newrelic.sli.good) / count(newrelic.sli.valid) * 100, 100) as 'SLI attainment' WHERE sli.guid = 'GUID'
eg.2 FROM Metric SELECT apm.service.apdex

Steps to Reproduce

• Add Status Widget Pack to an account.
• Launch and select "NRQL Status Widget" to configure
• Configure and add Query retrieving data from Metric

Expected Behaviour

Show and process Metrics in the widget.

Description

Using version 2.12.1 from the catalog, adding an on click URL doesn't redirect to the URL when clicking.

Steps to Reproduce

I added a query, of Workload status (FROM WorkloadStatus SELECT latest(statusValueCode) WHERE entity.name = 'thename'), changed the bucket size to 5 mins, added above thresholds with labels, selected display timeline, and added an on click URL.

Clicking on the widget in the dashboard does not redirect. Otherwise the widget works as expected.

Expected Behaviour

Redirect to URL.

Relevant Logs / Console output

No noticeable console errors while clicking, network shows a call to the event API.

Your Environment

• NR1 CLI version used: Catalog version of app.
• Browser name and version: FF (Version 92.0 (64-bit)) and Chrome (Version 93.0.4577.82 (Official Build) (x86_64)) with same results
• Operating System and version: Mac Big Sur 11.6

Additional context

Permalink, if that helps: https://onenr.io/0a7j9nE4mQO

Hi

Add support for nested queries with facet.
For example, the following query which measures the p99 time for some internal process within our system, is rejected by the widget because of the use of facet in the inner query, although the outer query is in fact valid for the widget.

select 
  percentile(avg_processing_time_min, 99)
from(
  select 
    average(totango.account_updater.total_process_time.percentiles)/60000 as 'avg_processing_time_min' 
  from 
    Metric 
  where 
    env = 'prod' and 
    percentile = '99' and 
    source != 'Pixel' 
  facet type)

New Relic UI uses the following colors to indicate Healthy, Warning and Critical status, it would be nice to match this color scheme.
Red - #a1251a
Yellow - #f8d45c
Green - #3a845e

It would be nice to have more control over the layout of charts in the modal page.
As a minimum, I'd like to be able to have a singe table chart maxed-out on the entire modal page.

Hello,

The following query:

select average(aws.rds.CPUUtilization) from Metric where aws.rds.DBInstanceIdentifier = 'data-db-prod' and tags.env = 'prod' 

Works perfectly in the platform's query builder, but doesn't seem to work in the status widget.
Maybe it's connected to the "Your Metric query has been transformed into a query that is compatible with the previous Infrastructure metric format." message?

Repolinter Report

🤖This issue was automatically generated by repolinter-action, developed by the Open Source and Developer Advocacy team at New Relic. This issue will be automatically updated or closed when changes are pushed. If you have any problems with this tool, please feel free to open a GitHub issue or give us a ping in #help-opensource.

This Repolinter run generated the following results:

• Fail
  • ❌ readme-starts-with-nr1-catalog-header
  • ❌ readme-contains-forum-topic
• Passed
  • ✅ license-file-exists
  • ✅ readme-file-exists
  • ✅ readme-contains-security-section
  • ✅ readme-contains-link-to-security-policy
  • ✅ third-party-notices-file-exists
  • ✅ code-of-conduct-should-not-exist-here
  • ✅ github-actions-workflow-file-exists
  • ✅ nr1-catalog-config-file-exists
  • ✅ nr1-catalog-screenshots-directory-exists
  • ✅ nr1-catalog-documentation-file-exists
  • ✅ package-scripts-present

Fail #

❌ readme-starts-with-nr1-catalog-header #

The README of a community plus project should have a NR1 Catalog header at the start of the README. If you already have a NR1 Catalog header and this rule is failing, your header may be out of date, and you should update your header with the suggested one below. For more information please visit https://opensource.newrelic.com/oss-category/. Below is a list of files or patterns that failed:

• README.md: The first 1 lines do not contain the pattern(s): Open source NR1 Catalog header (see https://opensource.newrelic.com/oss-category).
  • 🔨 Suggested Fix: prepend the latest code snippet found at https://github.com/newrelic/opensource-website/wiki/Open-Source-Category-Snippets#code-snippet-3 to file

❌ readme-contains-forum-topic #

Doesn't contain a link to the appropriate forum.newrelic.com topic (README.md). New Relic recommends directly linking the your appropriate forum.newrelic.com topic in the README, allowing developer an alternate method of getting support. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

Passed #

Description

Entity Status Widget is returning no entities found I believe due to this graphql call throwing deprecated errors.

Steps to Reproduce

1. Input a valid custom entity search query
2. See results

Possible Solution

Switch relationshipQuery to the following, using non-deprecated fields:

{
  actor {
    entities(guids: [${guids}]) {
      account {
        id
        name
      }
      guid
      name
      domain
      type
      entityType
      reporting
      ... on AlertableEntity {
        alertSeverity
      }
      relatedEntities {
        results {
          source {
            entity {
              name
              guid
              entityType
              ... on AlertableEntityOutline {
                alertSeverity
              }
            }
          }
          target {
            entity {
              name
              guid
              entityType
              ... on AlertableEntityOutline {
                alertSeverity
              }
            }
          }
        }
      }
    }
  }
}

Hi guys,

I'd like to have the warning threshold be optional. I want to use the NRQL status widget to determine if something is healthy or not based on the values 0 and 1. Therefore, I have no need for a warning threshold but this is not optional. Unless there is already a way to not have a warning threshold?

need to be able to set the order of the columns, for example, I may want my facet column to be on the far left..

I'm using simple color thresholds green, yellow and red.
These are returned from the Elasticsearch integration via select latest(cluster.status) from ElasticsearchClusterSample where entityName = 'es-cluster:my_cluster'

Regardless of the value returned from the query, the widget stays green.
Interestingly, the time line is rendered as expected.

Summary

In the NRQL Status Widget (and possibly others), when choosing the Display Metric option, the metric value is unformatted, with the exception of the Decimal Places selection. I would like to be able to format the metric value just like any other value in a built-in NR widget.

Desired Behaviour

I would like to see the same Data Format options available for the built-in NR widgets, specifically, the Number type's Autoformat option that will convert 3456 to 3.45 k, following the Decimal Places selection.

Additional context

I have a mix of built-in NR widgets and NRQL Status Widgets on my dashboard, and would like to see all of the values formatted the same way.