-
Notifications
You must be signed in to change notification settings - Fork 167
Add entites for Agent - GW setup #6311
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
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6311 +/- ##
==========================================
+ Coverage 36.83% 44.81% +7.97%
==========================================
Files 381 390 +9
Lines 26732 26995 +263
==========================================
+ Hits 9848 12099 +2251
+ Misses 15908 14023 -1885
+ Partials 976 873 -103 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
c3e6f71
to
27e55e5
Compare
Signed-off-by: Dani Louca <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have much context for this change, please let me know if I'm misunderstanding anything here.
Have you been able to test the routing connector functionality added here?
# Use instead when sending to gateway | ||
# endpoint: http://${SPLUNK_GATEWAY_URL}:4318 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# Use instead when sending to gateway | |
# endpoint: http://${SPLUNK_GATEWAY_URL}:4318 | |
# Use instead when sending to gateway | |
# endpoint: ${SPLUNK_GATEWAY_URL}:4318 |
Is http://
required here? Same question for other usages. I'm wondering why the value provided isn't consistent with usage of other environment variables.
@@ -142,6 +142,22 @@ exporters: | |||
token: "${SPLUNK_ACCESS_TOKEN}" | |||
endpoint: "${SPLUNK_INGEST_URL}/v1/log" | |||
log_data_enabled: false | |||
# To send entities (applicable only if discovery mode is enabled) | |||
otlphttp/entities: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is only relevant when discovery is enabled, is there some way to tie this to discovery mode? (The pipeline is only enabled when discovery mode is enabled?)
default_pipelines: [logs] | ||
table: | ||
- context: log | ||
condition: instrumentation_scope.attributes["otel.entity.event_as_log"] == true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where does otel.entity.event_as_log
come from? Is there some way we could use a central variable or constant here? Not required as it might be a bit messy, just concerned about the possibility of this changing in the future.
I haven't seen that
Please check to make sure it's not caused by this PR, we can address later if it's unrelated. |
Description:
Link to Splunk idea: <Link to Splunk idea, see https://ideas.splunk.com>
Testing:
Documentation: