Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Adding candidate and relationship btw OTel and kinesis stream #1744

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 3 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
16 changes: 16 additions & 0 deletions relationships/candidates/AWSKINESISSTREAM.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
category: AWSKINESISSTREAM
lookups:
- entityTypes:
- domain: INFRA
type: AWSKINESISSTREAM
tags:
matchingMode: ALL
predicates:
- tagKeys: ["aws.Arn"]
field: cloudResourceId
onMatch:
onMultipleMatches: RELATE_ALL
onMiss:
action: CREATE_UNINSTRUMENTED
uninstrumented:
type: AWSKINESISSTREAM
22 changes: 22 additions & 0 deletions relationships/synthesis/EXT-SERVICE-to-INFRA-KINESISSTREAM.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
relationships:
- name: extServiceCallsInfraKinesisStream
version: "1"
origins:
- Distributed Tracing
conditions:
- attribute: eventType
anyOf: [ "Span" ]
- attribute: rpc.service
anyOf: [ "kinesis" ]
Comment on lines +6 to +10
Copy link
Contributor

Choose a reason for hiding this comment

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

this condition will relate anything that has a span with rpc.service=kinesis.

not sure I follow how we are making sure is ext-service/otel only

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If we're primarily receiving data in spans, i guess we should opt for:
origins: - Distributed Tracing
instead of
origins: - Opentelemetry
Currently, no pull request exists for APM to AWS Kinesis streaming. We anticipate that APM data will continue to arrive in span format; if it's in metrics, we'll use APM Metrics. Do we need to wait for the APM to AWS Kinesis stream PR?

relationship:
expires: P75M
relationshipType: CALLS
source:
extractGuid:
attribute: entity.guid
target:
lookupGuid:
candidateCategory: AWSKINESISSTREAM
fields:
- field: cloudResourceId
attribute: cloud.resource_id
Loading