Jira (PDB-3600) PuppetDB should track how long each migration takes

2018-02-13 Thread Zachary Kent (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary Kent updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3600  
 
 
  PuppetDB should track how long each migration takes   
 

  
 
 
 
 

 
Change By: 
 Zachary Kent  
 
 
Release Notes Summary: 
 Time migrations and log them to make testing/support awareness easier.  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3600) PuppetDB should track how long each migration takes

2018-02-09 Thread Zachary Kent (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary Kent updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3600  
 
 
  PuppetDB should track how long each migration takes   
 

  
 
 
 
 

 
Change By: 
 Zachary Kent  
 
 
Fix Version/s: 
 PDB 5.2.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3600) PuppetDB should track how long each migration takes

2017-12-12 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-3600 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PuppetDB should track how long each migration takes  
 
 
 
 
 
 
 
 
 
 
Not super against it, but the logging approach seems like the cheapest way to make it valuable to the user. In my mind users mostly care about having this immediately visible (e.g logs) rather than requiring us to tell them about summary stats, etc. In any case this in incremental progress. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3600) PuppetDB should track how long each migration takes

2017-12-12 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker commented on  PDB-3600 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PuppetDB should track how long each migration takes  
 
 
 
 
 
 
 
 
 
 
Wyatt Alt are you opposed to storing this in the database? I figured if we put it in the DB then we could pull it out via summary_stats and compare. If it's in logs it won't be as persistent.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3600) PuppetDB should track how long each migration takes

2017-12-12 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3600 
 
 
 
  PuppetDB should track how long each migration takes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Team:
 
 Data Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3600) PuppetDB should track how long each migration takes

2017-06-27 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3600 
 
 
 
  PuppetDB should track how long each migration takes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/06/27 1:21 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Nick Walker 
 
 
 
 
 
 
 
 
 
 
The Problem 
Occasionally migrations take a while to complete but we can't compare how long any of them take. If we tracked them we could see during our internal testing and reports from users how long the migrations take and correlate that with other pieces of data that influence that.  
Suggested Solution  
Track the migration start, end, and duration in a schema_migrations_duration table or something like it.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment