Project

General

Profile

Actions
Copy link

User story #3945

closed

Store agent executions history in a 'lightweight' table, to speed up Rudder web interface

Added by Vincent MEMBRÉ about 11 years ago. Updated almost 6 years ago.

Status:
Released
Priority:
2
Assignee:
Vincent MEMBRÉ
Category:
Web - Compliance & node report
Target version:
2.8.0~beta1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Looking for agent executions is very ressource consumming in Rudder for now (ie : opening list nodes page is very very long if you got numerous nodes, be causeit is looking for the latest reports from each node)

If we had a completely separated table only containing executions, this would really ease the process (very few lines compared to millions in rudderSysEvents)

An agent execution consists in:
- The Id of the node executing the agent
- The time when that execution was ran
- If this execution was complete or not

We should have an actor parsing reports, regularly ran(~ every ten seconds, configurable), getting new reports and determine agent executions

Subtasks 5 (0 open — 5 closed)

User story #3946: Add all mechanisms to store agent executionsReleasedNicolas CHARLES2013-09-19Actions
User story #3947: Add call to execution repository when neededRejectedVincent MEMBRÉ2013-09-20Actions
User story #4059: Create migration script to create the database for node executions (rudder part)ReleasedFrançois ARMAND2013-10-11Actions
User story #4068: Add migration script for 'execution reports' processReleasedJonathan CLARKE2013-10-14Actions
User story #4069: Have meaningful properties name for the service that fetches agent run timesReleasedJonathan CLARKE2013-10-14Actions
Actions
Copy link

Also available in: Atom PDF