Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions ambassador/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: ambassador-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
6 changes: 6 additions & 0 deletions bonsai/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: bonsai-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
6 changes: 6 additions & 0 deletions emnify/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: emnify-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
6 changes: 6 additions & 0 deletions gnatsd/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: gnatsd-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
11 changes: 11 additions & 0 deletions gnatsd_streaming/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
provides:
- id: gnatsd-streaming-metrics

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Declare the NATS Streaming event flow

When a fault-tolerant NATS Streaming server changes state, gnatsd_streaming.py submits a failover event, and test_failover_event verifies that behavior. Listing only metrics therefore hides an event type that the check actively provides from dataflow consumers; add a gnatsd-streaming-events inbound entry.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed and fixed. _failover_check submits a real event (covered by test_failover_event), matching the existing direction: inbound, data_type: events precedent (e.g. redis-sentinel-events, gatling-enterprise-events). Added gnatsd-streaming-events.

always_on: true
granular: false
data_type: metrics
direction: inbound
- id: gnatsd-streaming-events
always_on: true
granular: false
data_type: events
direction: inbound
6 changes: 6 additions & 0 deletions k6/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: k6-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
11 changes: 11 additions & 0 deletions launchdarkly/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
provides:
- id: launchdarkly-metrics

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Declare LaunchDarkly's event flow

When customers configure the documented LaunchDarkly events integration, flag, project, and environment events are sent into Datadog (launchdarkly/README.md, lines 21–23 and 61–63), and the manifest sets creates_events to true. This metrics-only declaration consequently makes catalog consumers miss a supported data type; add a launchdarkly-events inbound entry.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed and fixed. Manifest sets creates_events: true and the README documents the events integration pushing flag/project/environment events into Datadog via API key (inbound, not an outbound notification tile). Added launchdarkly-events.

always_on: true
granular: false
data_type: metrics
direction: inbound
- id: launchdarkly-events
always_on: true
granular: false
data_type: events
direction: inbound
6 changes: 6 additions & 0 deletions mergify/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: mergify-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
6 changes: 6 additions & 0 deletions mergify_oauth/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: mergify-oauth-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
11 changes: 11 additions & 0 deletions modal/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
provides:
- id: modal-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
- id: modal-logs
always_on: true
granular: false
data_type: logs
direction: inbound
6 changes: 6 additions & 0 deletions ocient/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: ocient-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
6 changes: 6 additions & 0 deletions perimeterx/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: perimeterx-logs
always_on: true
granular: false
data_type: logs
direction: inbound
6 changes: 6 additions & 0 deletions qdrant/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: qdrant-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
6 changes: 6 additions & 0 deletions redis_cloud/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: redis-cloud-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
6 changes: 6 additions & 0 deletions redis_enterprise/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: redis-enterprise-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
6 changes: 6 additions & 0 deletions redis_enterprise_prometheus/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: redis-enterprise-prometheus-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
11 changes: 11 additions & 0 deletions redpanda/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
provides:
- id: redpanda-metrics

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Declare Redpanda's log flow

When users enable the shipped Redpanda log configuration, the Agent collects journald logs with source: redpanda (redpanda/assets/configuration/spec.yaml, lines 38–41), and the manifest also declares that log source. Because this file lists only metrics, dataflow consumers will incorrectly treat Redpanda as not providing logs; add a redpanda-logs inbound entry.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed and fixed. Verified against tidb-logs — same shape (journald-only logs template in spec.yaml, no assets/logs/ pipeline) and already merged as precedent (#3100). Added redpanda-logs.

always_on: true
granular: false
data_type: metrics
direction: inbound
- id: redpanda-logs
always_on: true
granular: false
data_type: logs
direction: inbound
11 changes: 11 additions & 0 deletions reflectiz/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
provides:
- id: reflectiz-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
- id: reflectiz-logs
always_on: true
granular: false
data_type: logs
direction: inbound
11 changes: 11 additions & 0 deletions rigor/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
provides:
- id: rigor-metrics

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Declare Rigor's event flow

When a Rigor check crosses its alert threshold or recovers, the integration pushes an event into Datadog (rigor/README.md, lines 117–124), consistent with the manifest's creates_events: true. Declaring only metrics causes dataflow consumers to omit this supported event stream; add a rigor-events inbound entry.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed and fixed. Manifest sets creates_events: true and the README documents Failed/Back-online events pushed into Datadog. Added rigor-events.

always_on: true
granular: false
data_type: metrics
direction: inbound
- id: rigor-events
always_on: true
granular: false
data_type: events
direction: inbound
6 changes: 6 additions & 0 deletions rundeck/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: rundeck-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
11 changes: 11 additions & 0 deletions sigsci/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
provides:
- id: sigsci-metrics

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Declare Signal Sciences' event flow

When Signal Sciences flags an IP address, the integration sends an event to the Datadog Event Stream (sigsci/README.md, lines 90–92), and its manifest explicitly sets creates_events to true. The metrics-only file therefore underreports the integration's provided data types; add a sigsci-events inbound entry.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed and fixed. Manifest sets creates_events: true and the README documents events sent to the Datadog Event Stream when an IP is flagged. Added sigsci-events.

always_on: true
granular: false
data_type: metrics
direction: inbound
- id: sigsci-events
always_on: true
granular: false
data_type: events
direction: inbound
6 changes: 6 additions & 0 deletions stardog/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: stardog-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
6 changes: 6 additions & 0 deletions sym/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: sym-logs
always_on: true
granular: false
data_type: logs
direction: inbound
6 changes: 6 additions & 0 deletions vespa/assets/dataflows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
provides:
- id: vespa-metrics
always_on: true
granular: false
data_type: metrics
direction: inbound
Loading