Project

General

Profile

Actions
Copy link

User story #5809

closed

Report metrics

Added by Benoît PECCATTE over 9 years ago. Updated over 9 years ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
Performance and scalability
Target version:
3.0.0~beta1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

To better understand our users use cases, we should report some metrics to users and to ourselves.

example of metrics :
- Number of rules
- Number of directives
- Number of nodes

Subtasks 8 (0 open — 8 closed)

User story #5810: Implement a command to collect and send metrics ReleasedJonathan CLARKE2014-11-24Actions
User story #5822: Add placeholder rudder metrics script to packagingReleasedJonathan CLARKE2014-11-26Actions
User story #5844: Add property to set metrics collection in RudderReleasedFrançois ARMAND2014-11-27Actions
User story #5847: Add system variable 'Send_Metrics' in cf-clerckReleasedFrançois ARMAND2014-11-27Actions
User story #5879: Metrics script: Pass options to curl to ensure that it follows redirects and POSTs content anywayReleasedMatthieu CERDA2014-11-29Actions
User story #5827: Add a technique to send send metrics ReleasedJonathan CLARKE2014-11-29Actions
Bug #5876: Missing report for metrics sending if it is disabledReleasedNicolas CHARLES2014-11-29Actions
Bug #5838: Clean up rudder-toolsReleasedJonathan CLARKE2014-11-27Actions

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #5883: Missing system variables for RUDDER_HEARTBEAT_INTERVAL and SEND_METRICS in TechniquesReleasedNicolas CHARLES2014-11-29Actions
Actions
Copy link

Also available in: Atom PDF