issues
search
MrAlias
/
otel-schema
Playground to prototype and investigate configuration schema proposals for OpenTelemetry
Apache License 2.0
2
stars
7
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
python config prototype
#54
ocelotl
opened
1 year ago
0
updated JSON requirement from MUST to MAY
#53
martinkuba
closed
1 year ago
0
Downgrade configuration model requirement from MUST to MAY
#52
jack-berg
closed
1 year ago
0
Add otep section on env var substitution
#51
jack-berg
closed
1 year ago
0
more updates to the otep
#50
codeboten
closed
1 year ago
0
Javascript configuration prototype
#49
martinkuba
opened
1 year ago
0
remove duplicate file
#48
codeboten
closed
1 year ago
0
replace name with type where it makes more sense
#47
codeboten
closed
1 year ago
0
Generate classes from json schema, demo parsing
#46
jack-berg
closed
1 year ago
0
Delete remnan json schems
#45
jack-berg
closed
1 year ago
0
python configuration prototype
#44
codeboten
closed
9 months ago
3
update otep to include recommendations from this week's call
#43
codeboten
closed
1 year ago
0
Update java json schema validation
#42
jack-berg
closed
1 year ago
0
python protobuf validation
#41
martinkuba
opened
1 year ago
0
Inconstistencies in use of key or `name` to declare type
#40
tsloughter
closed
1 year ago
0
jsonschema validation in go
#39
codeboten
closed
1 year ago
0
jsonschema validation in python
#38
codeboten
closed
1 year ago
1
update cuelang schema to match desired config
#37
tsloughter
opened
1 year ago
1
How is validation implemented for instrumentations?
#36
codeboten
opened
1 year ago
2
Add sampler configuration to example config.yaml
#35
jack-berg
closed
1 year ago
0
adding examples that are used in the OTEP
#34
codeboten
closed
1 year ago
0
Add prometheus config to example config.yaml
#33
jack-berg
closed
1 year ago
0
Add attribute limits to example config.yaml
#32
jack-berg
closed
1 year ago
0
starting on filling in internal details
#31
codeboten
closed
1 year ago
2
Document known limitations in otep
#30
codeboten
opened
1 year ago
1
Should config validation ensure configured components are available?
#29
codeboten
opened
1 year ago
2
update version name
#28
codeboten
closed
1 year ago
0
Add view configuration
#27
jack-berg
closed
1 year ago
0
Add propagators configuration
#26
jack-berg
closed
1 year ago
0
Add details for otlp and jaeger trace exporters
#25
jack-berg
closed
1 year ago
1
How to handle pull based metric exporters like prometheus
#24
jack-berg
closed
1 year ago
1
update otep
#23
codeboten
closed
1 year ago
0
Support log appender/handler configuration
#22
codeboten
opened
1 year ago
4
Configuration for semantic attributes collection
#21
svrnm
opened
1 year ago
2
Add logger_provider exporter and log_record_processors
#20
jack-berg
closed
1 year ago
0
Add meter_provider exporters and metric_readers
#19
jack-berg
closed
1 year ago
0
add otep template
#18
codeboten
closed
1 year ago
0
Add tracer_provider exporters and span_processors
#17
jack-berg
closed
1 year ago
0
Add span processors configuration
#16
jack-berg
closed
1 year ago
1
Define versioning
#15
pellared
closed
1 year ago
3
add initial options for SDK configuration
#14
codeboten
closed
1 year ago
0
add version to config file
#13
codeboten
closed
1 year ago
0
Should exporter configuration be nested or at top level?
#12
jack-berg
closed
1 year ago
4
Include config schema version
#11
jack-berg
closed
1 year ago
1
Decide what configuration lives in "root" of schema
#10
jack-berg
closed
1 year ago
1
adding usage options
#9
codeboten
closed
1 year ago
1
Compile examples of instrumentation and language specific configuration options
#8
jack-berg
opened
1 year ago
4
wip: cuelang proof of concept
#7
tsloughter
closed
1 year ago
0
add example configuration
#6
codeboten
closed
1 year ago
13
Propose "ideal" configuration
#5
codeboten
closed
1 year ago
10
Next