README.md says:

Please refer to the Agent user documentation for information about differences between Agent v5, Agent v6 and Agent v7.

However, these aren't easy to find in the documentation.

What is frustrating you?
The $content-width SCSS variable, found in frontend/src/component/styles/dimension.scss is set to 1200px currently, which works for desktop, but does not make sense for mobile. Components affected are: Header, Footer (but it looks fine since it's centered and just text), Section, and UserShortLinksSection.

Your solution
Refactor so that the `$con

Additional environment details (Operating System, Cloud provider, etc):

Steps to reproduce the issue:

1. Consul setup with helm charts on k8s. It is configured for TLS with a cert issued by the internal k8s CA.
2. Install DD Agent per https://app.datadoghq.com/account/settings#agent/kubernetes
3. Configure auto discovery on the Consul STS with the following annotations:

the utility scripts overwrites existing files and configuration as it executes each instruction.
In case the script fails for some reason, all the modified files are left as it is, which sometimes corrupts the existing configuration.

It will be useful if the script backup relevant files and restore them in case of error.

I love the tool, but I cannot embed non-https sources in my Grafana environment. It's unclear to me how to do this using the docker deployment method.

I'll be sure to add the docs myself if I figure it out!

Tags are a slice of strings in the documentation, but datadog-go documentation does not mention valid values for tags. datadog-go removes newlines from tags, but does not remove/escape other invalid characters like comma (,). Comma in tag value will be interpreted as multiple tags since tags are comma-separated in the UDP datagrams.

The page at https://docs.datadoghq.com/developers/guide/wh

In tracer version 2, we want to prefix span tag key constant (SpanType, etc) with "Key*" (KeySpanType, etc) to more easily differentiate between constants representing tag values and constants representing keys.
https://github.com/DataDog/dd-trace-go/blob/v1/ddtrace/ext/tags.go

I figured out my akka app wasn't showing any metrics.
I was using

import akka.http.scaladsl.Http2
    Http2().bindAndHandleAsync(...)

but the supported classpath is

import akka.http.scaladsl.Http
    Http().bindAndHandleAsync(...)

In order to avoid issues like #249 and #248 in the future, we should add a script to check these things in the CI builds. I'm open to ideas as to how we accomplish this. :)

We need to update https://github.com/DataDog/dd-trace-py/blob/master/docs/index.rst after #1123

I'm trying to figure out how to propagate contexts. In this example, the variable scope is assigned twice but only used once. Is the other one supposed to be used? Are there lines missing from the example?

const tracer = require('dd-trace').init({ plugins: false })
const express = require('express')
const app = express()

app.use((req, res, next) => {
  const span = trace

Hi there,

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

Terraform Version

0.12.18

Affected Resource(s)

• datadog_integration_gcp

Terraform Configuration Files

resource "google_service_a

As you can see with the link below, in documentation sampleRate is explained as percentage which causes some users to use values between 0-100 but expected value is actually between 0-1. Could you please update the documentation to sth like:

sampleRate:
 rate of the sampling (expected value between 0.0 and 1.0)

https://github.com/DataDog/java-dogstatsd-client/blob/2c972e6f011e6524

Documentation Page

https://docs.datadoghq.com/getting_started/tracing/

Issue Description

I've just spend some time fixing interoperability issues related to Datadog and some of our services using Kamon to report metrics.

In theory Kamon has a Datadog reporter module, in practice we had to replace Kamon's default implementation of trace id/span id identifiers which assumed the ide

Right now documentation says, that for Metrics send_all and send functions, we can pick one of 2 metric types:
metric_type|type: the type of metric to use ("gauge" or "count") [default: gauge]
and it's no longer true.

Since DataDog supports metric type "rate" and this library doesn't do any type validation, "rate" metric type is correctly supported by those functions.

Documentation f

Following the datadog Chef installation instructions on Chef 14 results in the following error:

$ knife cookbook site install datadog

[...unrelated output cut for brevity...]

Installing chef_handler to /home/joe/chef/cookbooks
Checking out the master branch.
Pristine copy branch (chef-vendor-chef_handler) exists, switching to it.
WA

The prometheus plugin uses metric names like this:

• org_graylog2_inputs_gelf_tcp_GELFTCPInput_5cc1bd20057c5200116dfdef_open_connections
• org_graylog2_lookup_adapters_5cc1bc798e510600109570d9_refresh_count
• org_graylog2_lookup_caches_5ca37df31210da0011143090_hits_total

It is really painful to write alarms for metrics like this. It would much better if the metrics would have names like th