chore(ui): adding support for Datadog Data Store #1972
Conversation
danielbdias
changed the title
danielbdias
force-pushed
the
add/datadog-data-source
branch
from
fd085d5
to
d880978
Compare
| @@ -2,7 +2,7 @@ type: Test | |||
| spec: | |||
| id: W656Q0c4g | |||
| name: http://app:8080 | |||
| description: akadlkasjdf | |||
| description: Calling Hello World API | |||
There was a problem hiding this comment.
What was the problem with akadlkasjdf?
There was a problem hiding this comment.
My documentation OCD won't free me if I don't update this description 😂
There was a problem hiding this comment.
Hey @danielbdias looks great. I think we need to add some support in the server code too. Please take a look at
|
@jorgeepc nice catch, I thought there was a BE PR checking that scenario! |
danielbdias
force-pushed
the
add/datadog-data-source
branch
from
c0a9bd3
to
f44bd90
Compare
| type: DataStore | ||
| spec: | ||
| name: OpenTelemetry Collector pipeline | ||
| type: otlp |
There was a problem hiding this comment.
should the type be datadog here? I know it's going to work with otlp, but to be able to display the proper selected option in the UI should we have datadog here?
There was a problem hiding this comment.
I believe that we can change this for Datadog. I'll do this on the next PR, that handles examples and documentation.
This PR adds support for Datadog as trace data store. The configuration page follows the same model as the Lightstep and New Relic integrations:
Changes
Configuration -> Connecting to Data Stores -> DatadogFixes
Checklist