Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
dcdb
dcdb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • dcdb
  • dcdbdcdb
  • Issues
  • #21

Closed
Open
Opened Dec 17, 2019 by Alessio Netti@di52bulMaintainer

Management of default TTL values

As of now, the values of a sensor always use its own TTL. If this value is defined for the sensor, the data will expire according to it, otherwise a default TTL of 0 is used, and the data never expires. The TTL value defined in the Collect Agent configurations is used only for sensors which are not published (no entry in the publishedsensors table).

We should evaluate whether it would be convenient or not to use the Collect Agent's TTL value also when a sensor is published, but has no TTL value associated to it, and not only when the sensor is not published at all.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dcdb/dcdb#21