You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[receiver/jaegerreceiver] Add logs when the respective server starts in jaegerreceiver (open-telemetry#36961)
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
- This PR adds the logging related to the server starting under the
[jaegerreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/jaegerreceiver)
- Added logs when: GRPC, Thrift Http, Thrift Binary and Thrift compact
server starts
<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixesjaegertracing/jaeger#6412
#### How was change tested?
Running collector with `jaegerreceiver` enabled with its all transports
#### Output
```
@Saumya40-codes ➜ /workspaces/opentelemetry-collector-contrib (log-endpoints) $ ./bin/otelcontribcol_linux_amd64 --config config.yaml
2024-12-27T15:37:23.428Z info [email protected]/service.go:164 Setting up own telemetry...
2024-12-27T15:37:23.428Z info telemetry/metrics.go:70 Serving metrics {"address": "localhost:8888", "metrics level": "Normal"}
2024-12-27T15:37:23.428Z info builders/builders.go:26 Development component. May change in the future. {"kind": "exporter", "data_type": "traces", "name": "debug"}
2024-12-27T15:37:23.436Z info [email protected]/service.go:230 Starting otelcontribcol... {"Version": "0.116.0-dev", "NumCPU": 2}
2024-12-27T15:37:23.436Z info extensions/extensions.go:39 Starting extensions...
2024-12-27T15:37:23.436Z info [email protected]/trace_receiver.go:252 Starting UDP server for Binary Thrift {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:6831"}
2024-12-27T15:37:23.436Z info [email protected]/trace_receiver.go:274 Starting UDP server for Compact Thrift {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:6832"}
2024-12-27T15:37:23.436Z info [email protected]/trace_receiver.go:398 Starting HTTP server for Jaeger Collector {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:14268"}
2024-12-27T15:37:23.436Z info [email protected]/trace_receiver.go:423 Starting gRPC server for Jaeger Collector {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:14250"}
2024-12-27T15:37:23.436Z info [email protected]/service.go:253 Everything is ready. Begin running and processing data.
```
#### config file used
```
receivers:
jaeger:
protocols:
grpc:
endpoint: "0.0.0.0:14250"
thrift_http:
endpoint: "0.0.0.0:14268"
thrift_binary:
endpoint: "0.0.0.0:6831"
thrift_compact:
endpoint: "0.0.0.0:6832"
exporters:
debug: {}
service:
pipelines:
traces:
receivers: [jaeger]
exporters: [debug]
```
cc @fatsheep9146
---------
Signed-off-by: Saumyacodes-40 <[email protected]>
Co-authored-by: Yuri Shkuro <[email protected]>
# Use this changelog template to create an entry for release notes.
2
+
3
+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4
+
change_type: enhancement
5
+
6
+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7
+
component: jaegerreceiver
8
+
9
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10
+
note: Log the endpoints of different servers started by jaegerreceiver
11
+
12
+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13
+
issues: [36961]
14
+
15
+
# (Optional) One or more lines of additional information to render under the primary note.
16
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17
+
# Use pipe (|) for multiline entries.
18
+
subtext: |
19
+
This change logs the endpoints of different servers started by jaegerreceiver. It simplifies debugging by ensuring log messages match configuration settings.
20
+
21
+
# If your change doesn't affect end users or the exported elements of any package,
22
+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
23
+
# Optional: The change log or logs in which this entry should be included.
24
+
# e.g. '[user]' or '[user, api]'
25
+
# Include 'user' if the change is relevant to end users.
26
+
# Include 'api' if there is a change to a library API.
0 commit comments