Closed Bug 1340187 Opened 8 years ago Closed 8 years ago

Enable HTTP caching for telemetry aggregates

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1336000

People

(Reporter: rvitillo, Unassigned)

References

Details

User Story

HTTP caching should be enabled for telemetry aggregates:

- submission-date based aggregates should in theory be immutable; note that in some rare occasions a backfill might change a submission-date based aggregate though;
- "recent" build-id based aggregates should be cached for at most 24h; older build-id aggregates could be cached for longer periods as they change very slowly (if at all).
No description provided.
User Story: (updated)
User Story: (updated)
User Story: (updated)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.