Hot answers tagged log
History logs are stored in C:\Users\<user name>\AppData\(Local or LocalLow or Roaming)\ESRI\Desktop10.1\ArcToolbox\History but to save log history, you have to activate it, using this code : arcpy.SetLogHistory(True) EDIT: For Arcgis 10.0 ArcPy do not support SetLogHistory(), so you have to activate it manually like described in this link
Are you trying to do this in near real time with telemetry feedback to an R/C controller, or against a datalog after recovery? Either way have a look at your datastream or datalog file. Depending on the brand of GPS and type of data logging you might have full NMEA sentences, or just abreviated fixes to work with. If NMEA 183 sentences look ...
There are actually a number of ways of tracing any ArcSDE connection. Calls between the client application and the ArcSDE client are logged in the SDE Trace file, between the ArcSDE client and server in the SDE Intercept file, the ArcSDE server will log certain events in the service or direct connect log, and database calls are logged in the DBMS logfiles. ...
You can install and configure the logback tee filter as documented here: http://logback.qos.ch/access.html#teeFilter The Tee filter seems to dump both request and response headers. another solution builtin in geoserver, does not meet user requirements Edit the web.xml file in webapps/geoserver/WEB-INF/web.xml then scroll down until you reach the ...
Interesting question, these files have been around for a long time but no obvious explanation of their structure. I've noticed that they often log raster processing operations as does your example show. I came across these threads  but none of them explicitly describe the structure of the log file. I don't think its documented anywhere and probably ...
Edit the tomcat configuration file (in conf/server.xml) and add an AccessLog Valve. The common log format already logs the username along with url and is common in the sense that most log processing tool can process it out of the box.
I think your best bet here is a plugin, or some custom Python code that you can use for monitoring. If you place a startup.py script in .qgis/python it will be imported when QGIS starts so you could do something like this in there: import logging import getpass from qgis.core import QgsMapLayerRegistry QgsMapLayerRegistry.layersAdded.connect(loglayers) ...
In my experience with the Attribute Assistant, I found that you need to enter the actual field name not the alias in the FIELDNAME field of the DynamicValue table (e.g. ADDPTKEY instead of Address Point ID). Also, layer names in the TABLENAME field in the DynamicValue table should be the name of the feature class not what the layer is named in the table of ...
Today i stumbled on the same problem (Win 7 64-bit, QGis 1.8.0). In search of a solution i disabled all plugins (in the registry), deleted the .qgis folder, Qgis registry entries and reinstalled, but nothing helped. However, i had QGis working just fine about a week or two ago. My QGis was crashing when the splash screen displayed "Starting python" (or ...
This has helped me get this working: http://stackoverflow.com/questions/876239/bash-redirect-and-append-both-stdout-and-stderr Its called redirection. I have used 2>> filename.txt to redirect the error messages to a text file. I also found that using --debug ON in my ogr calls helped to give more verbose messages in the log file.
There is a utility available on ArcScripts - ServiceMonitor - which can let you get at least some monitoring on your services. I have not tested it myself though. Free apps are Apache JMeter and Fiddler. Commercial apps are GeoCortex and GeoXMF (tested myself, has support for 9.3).
It sounds like at the core, you are talking about data lineage; where the data came from and what has been done to it by whom. This, I believe, is a perfect use case for good metadata, which is some circles is quite the nasty word. However, you can manually enter your data lineage directly in your metadata, which would work, but isn't an automated process. I ...
I don't think there is a single tool, and this won't help you at 10.0, but Editor Tracking which was new in 10.1 should meet some of your requirements. Also, if you are interested in versioning of MXDs/LYRs then this is an ArcGIS Idea you may want to vote for.
Attribute Assistant is an absolutely marvelous instrument, too bad it doesn't work. My conclusion would be this: ESRI has way too little info on the methods used in Attribute Assistant so you could be doing anything wrong without even know it. I tend to think that the "layer not found" error appears when you don't make the right selection in a FC/ table.
Only top voted, non community-wiki answers of a minimum length are eligible