open-telemetry/opamp-spec

Issues

• PackageStatus message should define a downloading state and include additional metadata

  #204 opened 2 months ago by michel-laterman
  2

• Proposal for Add-On Configuration Support in OSS OpAMP Specification

  #202 opened 3 months ago by pavankrish123
  2

• Proxy & TLS settings in OpAMPConnectionSettings, TelemetryConnectionSettings, and OtherConnectionSettings

  #203 opened 3 months ago by michel-laterman
  1

• Agents should report supported components

  #198 opened 5 months ago by andykellr
  23

• Allow setting authentication in `DownloadableFile` message

  #194 opened 5 months ago by tpaschalis
  1

• OpAMP Agent heartbeats

  #183 opened 5 months ago by jaronoff97
  7

• Allow remote configuration of an agent's non-identifying attributes

  #185 opened 5 months ago by BinaryFissionGames
  1

• TLSCertificate.public_key is incorrectly named

  #161 opened 6 months ago by tigrannajaryan
  0

• Markdown link checking isn't working

  #170 opened 6 months ago by chalin
  1

• Add a field for non-config files to AgentRemoteConfig

  #184 opened 8 months ago by evan-bradley
  1

• Send minimal config updates on an established connection

  #182 opened 9 months ago by jaronoff97
  0

• Opamp spec overloads definition of service.name

  #131 opened 2 years ago by jack-berg
  13

• Spec contains an invalid links

  #169 opened a year ago by chalin
  1

• TelemetryConnectionSettings should support all config options of the exporter

  #177 opened a year ago by srikanthccv
  1

• Extend AgentHealth message to accommodate component health

  #165 opened a year ago by mwear
  13

• Need ability to report errors in response to Command and Connection Settings Offer

  #164 opened a year ago by tigrannajaryan
  0

• Security: Configuration Restrictions

  #119 opened 2 years ago by aiwaniuk
  3

• [editorial] Spec: replace links to semantic_conventions by semconv section of OTel website

  #150 opened a year ago by chalin
  0

• [editorial] Spec-status `[Beta]` markdown link definition isn't defined

  #157 opened a year ago by chalin
  0

• Declare stability per capability or for all spec?

  #146 opened a year ago by tigrannajaryan
  5

• [editorial] Update spec to make it suitable for publication on the OTel website

  #148 opened a year ago by chalin
  0

• Documentation: AgentRemoteConfig missing "config_hash" field

  #120 opened a year ago by davidmirza408
  0

• Explain why OpAMP client/server implementations may expose generated Protobufs in the API

  #140 opened a year ago by tigrannajaryan
  2

• Security: Add a mechanism for sending secrets that avoids embedding them in plain text configurations.

  #143 opened 2 years ago by nephyst
  0

• RemoteConfigStatus cannot return status per configuration passed in AgentRemoteConfig AgentConfigMap

  #144 opened 2 years ago by andykellr
  5

• Explain what "Stable" label means for OpAMP

  #134 opened 2 years ago by tigrannajaryan
  1

• Split specification into one page per main section

  #145 opened 2 years ago by chalin
  2

• Feature: Add attribute to Agent Capabilities for mechanism of sending Agent Description

  #142 opened 2 years ago by kailash-bhanushali
  3

• Clarify agent health reporting

  #136 opened 2 years ago by tigrannajaryan
  3

• Consider adding a header for WebSocket messages to allow future extensibility

  #133 opened 2 years ago by tigrannajaryan
  7

• Remove deleted wording from the spec

  #124 opened 2 years ago by tigrannajaryan
  0

• Change MAY to SHOULD for Server to Client compression?

  #123 opened 2 years ago by tigrannajaryan
  1

• Unable to set multiple Capabilities in a single message when using Java/Kotlin protobuf

  #121 opened 2 years ago by nephyst
  4

• Agent vs Client is a bit confusing

  #114 opened 2 years ago by tigrannajaryan
  3

• Security: Code Signing - downgrade prevention

  #118 opened 2 years ago by aiwaniuk
  0

• Confirm that WebSocket compression works

  #92 opened 2 years ago by tigrannajaryan
  1

• Require that instance_uid is ULID instead of only recommending it

  #113 opened 2 years ago by tigrannajaryan
  1

• Add ReportsRemoteConfig capability

  #112 opened 2 years ago by tigrannajaryan
  2

• Clarify how top-level and sub-packages can coexist

  #99 opened 2 years ago by tigrannajaryan
  3

• Remote management for the server

  #106 opened 2 years ago by Doron-Bargo
  1

• Consider adding a "status compressed/full" flag to AgentToServer

  #109 opened 2 years ago by tigrannajaryan
  7

• Status compression is complicated and confusing

  #101 opened 2 years ago by tigrannajaryan
  2

• Locally installed package reporting

  #96 opened 2 years ago by tigrannajaryan
  0

• Add infinite oscillations explanation to Status Reporting section

  #95 opened 2 years ago by tigrannajaryan
  0

• Support JSON-encoded Protobuf messages

  #94 opened 2 years ago by tigrannajaryan
  0

• Do we need to clarify how load balancing works with OpAMP

  #93 opened 2 years ago by tigrannajaryan
  0

• Do we need recommendation to cache remote config and OTLP metric destination

  #91 opened 2 years ago by tigrannajaryan
  0

• Need clarification on how OpAMP sends sensitive credential data to the client

  #80 opened 3 years ago by dsvanlani
  5

• Move messages in StatusReport to AgentToServer message

  #84 opened 3 years ago by tigrannajaryan
  2

• Add ability to report general errors in PackageStatuses

  #82 opened 3 years ago by tigrannajaryan
  0