EnviroDataR request logger

Introduction

Certain functions used in EnviroDataR also trigger the creation and update of an associated log file (edr_logs.txt) with useful metadata about each request made. Some of these functions include: * Add list of functions monitored by the logger * …

Creation and update of the logger file

The first time one of these functions is called, the log file is created in the same directory containing the R script where the function was called, typically ~\your-project-name\R\, and is updated with each successive call.

Types of logger messages

Request metadata

The logger logs useful metadata about the requests made including: * Names of analytes found at discrete monitoring locations. * The number of data points per analyte. * The number of data points per guideline. * A date and time stamp for each request conducted.

Request events

It also documents a number of important events including: * If a requested discrete/continuous monitoring location does not exist for the tenant. * If a request for a specific analyte/timeseries dataset yields zero data. * If a request for a guideline yields zero data.

Without breaking the flow of the function’s operation, an error or warning message is printed and logged in the logger file. If a requested station does not exist or some error has occurred for a request, the error is printed and logged and the function continues to the next station.