roadiehq/backstage-plugin-datadog

Embed Datadog graphs and dashboards into Backstage

backstage-plugin-datadog's Issues

Installation step 4 no longer works with version 0.2.1

Hey Guys

thanks for the project but I was just wondering if you could update the installation steps for version 0.2.1 as there only work for version 0.1.1

looks like a couple thing have been deprecated in the last version.

cheers

Documentation on main plugin site

Hey guys,

Just wondering if there were plans to update the documentation on here ? That documentation threw me off for a while because it's the main link on the Backstage site.

Happy to help if needed.

Josh

Dashboard with mutliple charts fails to load

Expected Behavior

You can view a dashboard url with multiple charts/widgets.

Current Behavior

Trying to view a dashboard with multiple widgets doesn't see to work and results in a datadog Oof error. It seems to be related to the appending of the tvmode query string. Removing it seems to avoid the error.

Possible Solution

I'm not sure what tvmode does, but is it necessary?

Steps to Reproduce

1. Create a Datadog dashboard with 5-6 charts
2. Configure the dashboard for sharing
3. Use the shared dashboard url on the datadog entity annotation
4. Try and view the dashboard

Context

Testing out the datadog plugin:

Your Environment

• Plugin Version: 0.2.1
• Backstage version: Up to date
• NodeJS Version: 14
• Operating System and Version: macOS
• Browser Information: chrome or ff

expected workspace package to exist for rollup-plugin-typescript2

Getting the following error when running the following in /packages/app: yarn add @roadiehq/backstage-plugin-datadog

error An unexpected error occurred: "expected workspace package to exist for "rollup-plugin-typescript2"".

Current Behavior

Possible Solution

Steps to Reproduce

1. Step 1
2. Step 2
3. ...

Context

Your Environment

• Plugin Version (version of this software e.g. v0.4.3):
• Backstage version (e.g. 0.1.1-alpha23):
• NodeJS Version (e.g. v12):
• Operating System and Version (e.g. Ubuntu 14.04):
• Browser Information (e.g. chrome 85):

Top level domain for the embedded graph url is fixed to .eu

Expected Behavior

Current Behavior

The url used for embedded graph it's using the eu as the top-level domain and it causes the graph to not be found. In our case we use .com

backstage-plugin-datadog/src/components/GraphWidget.tsx

Line 52 in 4e66aea

src={`https://app.datadoghq.eu/graph/embed?token=${graphToken}&height=${height}&width=${width}&legend=true`}

Possible Solution

Maybe add the url as a config or part of the annotations

Steps to Reproduce

Context

Your Environment

• Plugin Version (version of this software e.g. v0.4.3): 1.0.0
• Backstage version (e.g. 0.1.1-alpha23): 0.7.4
• NodeJS Version (e.g. v12):
• Operating System and Version (e.g. Ubuntu 14.04):
• Browser Information (e.g. chrome 85):

Installation steps are outdated after the backstage composability work.

Hi folks,

Steps mentioned in this page are not working anymore. Running into compile errors when trying to build the project. Seems like this is an issue later the composability work. Please help.

Thanks.

CSP Issue - Datadog Limitation?

Hi!

I've tried loading the plugin following the instructions (including adding the CSP settings), but it seems there might be some issue related to headers set by Datadog in order to prevent their stuff from being referenced from iframes?

When trying to use the EntityDataDogContent with a dashboard URL (e.g. https://app.datadoghq.com/dashboard/844435-e4p-vue/some_dashboard?from_ts=1669289464232&to_ts=1669293064232&live=true), I'm getting the following error:
Refused to frame 'https://app.datadoghq.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self'".

Any idea if this plugin still works?

Thanks!

Upgrade @backstage/core and @backstage/catalog-model to 0.7.x

Expected Behavior

That the yarn backstage-cli versions:check runs without any issues.

Current Behavior

It fails.

Possible Solution

Upgrade @backstage/core and @backstage/catalog-model to 0.7.x

Steps to Reproduce

1. Run This plugin prevents the yarn backstage-cli versions:check command to run successfully.
2. See it fail

Context

Your Environment

• Plugin Version (version of this software e.g. v0.4.3): 1.0.0

No Public Sharing

Can a different scenario be taken into consideration. This is the one in which you do NOT "public share" your dashboard, and if you do just do all the request via the backend not the frontend.

All of this comes because at our end we have the "pubblic share" whitelisted base on IPs, so it is not possible for a dev that is at home (and not connected to the VPN) to check the Datadog backstage plugin as it would be impossible to whitelist his/her IP.

Hope this easy explanation helps.

The datadog annotations should be prefixed with datadoghq.com

Expected Behavior

As per common backstage conventions for annotations, the left side of annotation typically matches the domain name of the company or organization (e.g. github.com, backstage.io, jenkins.io, etc.)

Current Behavior

The annotation for the plugin uses the prefix datadog/dashboard-url which doesn't map to a domain name of https://www.datadoghq.com/.

Possible Solution

Rename the annotation prefix to match datadoghq.com or datadog.com (which seems to redirect to the prior). For example datadoghq.com/dashboard-url

Steps to Reproduce

n/a