Sorry the description was unclear.

apmsoak uses a scenarios file to send load to the intake api. Each scenario can be customized by tuning specific settings:

Lines 11 to 27 in 83d2b40

    
           type ScenarioConfig struct { 
        
           	ProjectID                 string            `yaml:"project_id"` 
        
           	ServerURL                 string            `yaml:"server"` 
        
           	APIKey                    string            `yaml:"api_key"` 
        
           	AgentName                 string            `yaml:"agent_name"` 
        
           	AgentsReplicas            int               `yaml:"agent_replicas"` 
        
           	EventRate                 string            `yaml:"event_rate"` 
        
           	RewriteIDs                bool              `yaml:"rewrite_ids"` 
        
           	RewriteTimestamps         bool              `yaml:"rewrite_timestamps"` 
        
           	RewriteServiceNames       bool              `yaml:"rewrite_service_names"` 
        
           	RewriteServiceNodeNames   bool              `yaml:"rewrite_service_node_names"` 
        
           	RewriteServiceTargetNames bool              `yaml:"rewrite_service_target_names"` 
        
           	RewriteSpanNames          bool              `yaml:"rewrite_span_names"` 
        
           	RewriteTransactionNames   bool              `yaml:"rewrite_transaction_names"` 
        
           	RewriteTransactionTypes   bool              `yaml:"rewrite_transaction_types"` 
        
           	Headers                   map[string]string `yaml:"headers"` 
        
           }

Among those there is agent_name which allows us to choose specific agents. What I had in mind was to add support for something like agent_name: otlp.

AFAIK the events are hardcoded in the repository in ndjson files so we would need to store the otlp payload but I wouldn't focus too much on that. A basic/simple example is enough. We can then iterate and use a more realistic payload. WDYT ?

	type ScenarioConfig struct {
	ProjectID string `yaml:"project_id"`
	ServerURL string `yaml:"server"`
	APIKey string `yaml:"api_key"`
	AgentName string `yaml:"agent_name"`
	AgentsReplicas int `yaml:"agent_replicas"`
	EventRate string `yaml:"event_rate"`
	RewriteIDs bool `yaml:"rewrite_ids"`
	RewriteTimestamps bool `yaml:"rewrite_timestamps"`
	RewriteServiceNames bool `yaml:"rewrite_service_names"`
	RewriteServiceNodeNames bool `yaml:"rewrite_service_node_names"`
	RewriteServiceTargetNames bool `yaml:"rewrite_service_target_names"`
	RewriteSpanNames bool `yaml:"rewrite_span_names"`
	RewriteTransactionNames bool `yaml:"rewrite_transaction_names"`
	RewriteTransactionTypes bool `yaml:"rewrite_transaction_types"`
	Headers map[string]string `yaml:"headers"`
	}

feat: add support for otlp endpoints #18

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions