postgres-vacuum-monitor 0.4.0 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3185d7bfa19acb621c7c7f67c3239fa51f2dc1cc0e654ff71f2c708f6b082923
-  data.tar.gz: b78ffb48ba844d46d6dce24d2cf0fdb55f83805e17bdc7e5b6ede159666dfa1b
+  metadata.gz: e764680ab6a464db250c1c47b04cef57d9662760c388daf96bf73987f542ba2d
+  data.tar.gz: 6fca9d4989d2c9db092ff78a6ec2429053e0600b4ea1c31f1226d986c6cf20ef
 SHA512:
-  metadata.gz: dd4e24cbb07c4b38f91fd16a0e0f9026ced4d6584d93ee25c6d8ab9a5249948ed0f75301b42568bb0c8d441ba356aa33fad372ed4def3e586255eee5e82fa035
-  data.tar.gz: 8c154e6ad4867024f2676caa1aa467fceeba3c715c817264fac63c810ad1535aaf006733af304e395c96ea4cf6d7bc4bc2f88b6d81cdc67f45cc50663da36ebc
+  metadata.gz: 6477ea77d2c5b0d7e3f926ec794c69df057c7cc94026789e341c1e1318b8739e3d36d2eef26003b124ea7f63b10d74f6237ade609c6c2fa6d6986f399b6879df
+  data.tar.gz: 49b19ea6107c6771d7c3bce1690ba294cc8e0ecb9d378f0cb08afa574b6d99350c72201ced9390db7b2c55a516f4a6ce13b5dfa3638aa6bd2939160b6cc549d3

data/CHANGELOG.md

@@ -1,4 +1,9 @@
 # postgres-vacuum-monitor
+## v.0.5.0
+- Renamed `LongQueries` event to `LongTransactions`. 
+- Renamed `LongTransactions.query` to `LongTransactions.most_recent_query` and added a
+  transaction `state` attribute.
+
 ## v.0.4.0
   - Add rails 6 support.
 

data/README.md

@@ -8,7 +8,7 @@
 Postgres::Vacuum::Monitor provides queries that provide information about the number of dead tuples and long running queries.
 This information helps to diagnose and monitor two things: 
 1) That the current auto vacuum settings are working and keeping up.
-2) That there are no long running queries affecting the auto vacuuming daemon.
+2) That there are no long running transactions affecting the auto vacuuming daemon.
 
 ## Installation
 
@@ -44,14 +44,15 @@ class MetricsReporter
 end
 ```
 
-For long running queries, the event name is `LongQueries` and the attributes are: 
+For long running transactions, the event name is `LongTransactions` and the attributes are: 
 ```ruby 
 {
   database_name: # The name of the database.
-  start_time: # When the query started .
+  start_time: # When the transaction started .
   running_time: # How long has it been running in seconds.
   application_name: # What's the application name that is running the query.
-  query: # The offending query.
+  most_recent_query: # The last query started by the transaction
+  state: # The state of the transaction - either "active" or ""
 }
 ```
 
@@ -84,9 +85,9 @@ SELECT percentile(tuples_over_limit, 95) from AutoVacuumLagging facet table wher
 ```SQL
 SELECT percentile(dead_tuples) FROM AutoVacuumLagging facet table where appName = 'my-app' SINCE 1 DAY AGO TIMESERIES
 ```     
-#### Long running queries
+#### Long running transactions
 ```SQL
-SELECT application_name, query, running_time, start_time FROM LongQueries
+SELECT application_name, state, most_recent_query, running_time, start_time FROM LongTransactions
 ```
 
 #### Tables that need to be vacuumed

data/lib/postgres/vacuum/jobs/monitor_job.rb

@@ -3,25 +3,26 @@ module Postgres
     module Jobs
       class MonitorJob
 
-        AUTOVACUUM_QUERY_EVENT = 'AutoVacuumLagging'.freeze
-        LONG_QUERIES = 'LongQueries'.freeze
+        AUTOVACUUM_LAGGING_EVENT = 'AutoVacuumLagging'.freeze
+        LONG_TRANSACTIONS = 'LongTransactions'.freeze
 
         def perform(*)
           with_each_db_name_and_connection do |name, connection|
-            connection.execute(Postgres::Vacuum::Monitor::Query.long_running_queries).each do |row|
+            connection.execute(Postgres::Vacuum::Monitor::Query.long_running_transactions).each do |row|
               reporter_class.report_event(
-                LONG_QUERIES,
+                LONG_TRANSACTIONS,
                 database_name: name,
                 start_time: row['xact_start'],
                 running_time: row['seconds'],
                 application_name: row['application_name'],
-                query: row['query']
+                most_recent_query: row['query'],
+                state: row['state']
               )
             end
 
             connection.execute(Postgres::Vacuum::Monitor::Query.tables_eligible_vacuuming).each do |row|
               reporter_class.report_event(
-                AUTOVACUUM_QUERY_EVENT,
+                AUTOVACUUM_LAGGING_EVENT,
                 database_name: name,
                 table: row['relation'],
                 table_size: row['table_size'],

data/lib/postgres/vacuum/monitor/query.rb

@@ -11,7 +11,7 @@ module Postgres
         MAX_AGE_SETTING = "'autovacuum_freeze_max_age'".freeze
         PG_CATALOG = "'pg_catalog'".freeze
 
-        def long_running_queries
+        def long_running_transactions
           <<-SQL
             SELECT *
             FROM (
@@ -20,7 +20,8 @@ module Postgres
                 xact_start,
                 EXTRACT(EPOCH FROM (now() - xact_start)) AS seconds,
                 application_name,
-                query
+                query,
+                state
               FROM pg_stat_activity
               WHERE state IN (#{STATES.join(', ')})
               ORDER BY seconds DESC

data/lib/postgres/vacuum/monitor/version.rb

@@ -1,7 +1,7 @@
 module Postgres
   module Vacuum
     module Monitor
-      VERSION = '0.4.0'.freeze
+      VERSION = '0.5.0'.freeze
     end
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: postgres-vacuum-monitor
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.5.0
 platform: ruby
 authors:
 - Fernando Garces
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-09-24 00:00:00.000000000 Z
+date: 2020-02-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: appraisal
@@ -195,7 +195,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.4
+rubygems_version: 3.0.6
 signing_key: 
 specification_version: 4
 summary: Simple stats collector for postgres auto vacuumer.