Skip to main content
  • EN

The Dashboard data is great for seeing patterns over a period of 30 days but if the period were extended it could provide other information too. For example, "how long has it been since a certain workspace has been used?" That would identify FME scripts that are no longer being used.

It would be easy to build something that would store the daily data better than the current CSV files, for example, a SQLite database, and then build reports off of it. However, I'm wonder if Safe has something like this in the works already?

Hi @jimo

 

The FME Server database does record history longer than 30 days - which is where the CSV information is coming from.

 

The fme_job_history table has the request information which contains the workspace name. If you can read this, you could build your own dashboard to report unused workspaces.

Hi @jimo

 

The FME Server database does record history longer than 30 days - which is where the CSV information is coming from.

 

The fme_job_history table has the request information which contains the workspace name. If you can read this, you could build your own dashboard to report unused workspaces.
I might actually add some custom dashboards, thanks for the suggestion.

 

 

Hi @jimo

 

The FME Server database does record history longer than 30 days - which is where the CSV information is coming from.

 

The fme_job_history table has the request information which contains the workspace name. If you can read this, you could build your own dashboard to report unused workspaces.
How do I connect to postgres on the local machine? I have tried localhost at port 5432 but get "could not connect to server: Connection refused". I have my pg_hba.conf file configured for a remote engine, that is, " all all 0.0.0.0/0". Also, what account do I connect as?

 

 

How do I connect to postgres on the local machine? I have tried localhost at port 5432 but get "could not connect to server: Connection refused". I have my pg_hba.conf file configured for a remote engine, that is, " all all 0.0.0.0/0". Also, what account do I connect as?

 

 

If you're using the default database it's port 7082

 

 

Hi @jimo

 

The FME Server database does record history longer than 30 days - which is where the CSV information is coming from.

 

The fme_job_history table has the request information which contains the workspace name. If you can read this, you could build your own dashboard to report unused workspaces.
Okay, I can connect on localhost at port 7082 to database postgres with user/password fmeserver/fmeserver and database fmeserver. The user name and password are defined in the fmeCommonConfig.txt file.

 

 

Would be nice to have some official documentation on all this.

 

 

 

My fme_job_history table only goes back 5 days. I think that's because I set my "Remove Job History" to 4 days to conserve space on our VM.

I think if you wanted to save history for say, one year you would still have to store it elsewhere, else you would wind up with one year's worth of log files. This would be easy to do by just adding an SQLite writer to the JobHistoryStatisticsGathering.fmw script that populates the CSV files.

Okay, I can connect on localhost at port 7082 to database postgres with user/password fmeserver/fmeserver and database fmeserver. The user name and password are defined in the fmeCommonConfig.txt file.

 

 

Would be nice to have some official documentation on all this.

 

 

 

We don't want to make it easy for people to get access into those databases because if people make changes then there's a good chance it would break things on FME Server. So use the power wisely (read only)

Reply


Community Stats

30,469
Posts
115,703
Replies
38,290
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.