[{"_1":2,"_173":-5,"_174":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_152":153},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":85,"_107":108,"_145":-5,"_146":11,"_147":17,"_148":11,"_149":-5,"_150":151},"canonicalUrl","https://hub.docker.com/r/texastribune/prometheus-nginxlog-exporter/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","texastribune","reponame","prometheus-nginxlog-exporter","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2020-05-12T15:41:39.810786Z","description","","is_private","last_updated","2020-05-12T15:57:28.692607Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",2371,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","= NGINX-to-Prometheus log file exporter\n:tip-caption: :bulb:\n:note-caption: :information_source:\n:important-caption: :heavy_exclamation_mark:\n:caution-caption: :fire:\n:warning-caption: :warning:\n:toc:\n:toc-placement!:\n:toc-title:\n\nimage:https://img.shields.io/github/workflow/status/martin-helmich/prometheus-nginxlog-exporter/Compile%20&%20Test[GitHub Workflow Status]\nimage:https://quay.io/repository/martinhelmich/prometheus-nginxlog-exporter/status[link=\"https://quay.io/repository/martinhelmich/prometheus-nginxlog-exporter\",Docker Repository on Quay]\nimage:https://goreportcard.com/badge/github.com/martin-helmich/prometheus-nginxlog-exporter[link=\"https://goreportcard.com/report/github.com/martin-helmich/prometheus-nginxlog-exporter\", Go Report Card]\nimage:https://img.shields.io/github/license/martin-helmich/prometheus-nginxlog-exporter[GitHub]\nimage:https://img.shields.io/badge/donate-PayPal-yellow[link=\"https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=SEARYHPVS9U5N&source=url\", Donate]\n\nHelper tool that continuously reads an NGINX log file (or any kind of similar log file) and exports metrics to https://prometheus.io/[Prometheus].\n\n[discrete]\n== Contents\n\ntoc::[]\n\n== Usage\n\nYou can either use a simple configuration, using command-line flags, or create\na configuration file with a more advanced configuration.\n\nUse the command-line:\n\n[source]\n----\n$ ./prometheus-nginxlog-exporter \\\n -format=\"\" \\\n -listen-port=4040 \\\n -namespace=nginx \\\n [PATHS-TO-LOGFILES...]\n----\n\nUse the configuration file:\n\n[source]\n----\n$ ./prometheus-nginxlog-exporter -config-file /path/to/config.hcl\n----\n\nInstallation\n------------\n\nThere are multiple ways to install this exporter.\n\n=== Docker\n\nDocker images for this exporter are available at the quay.io and pkg.github.com\nregistries:\n\n - `quay.io/martinhelmich/prometheus-nginxlog-exporter:v1`\n - `docker.pkg.github.com/martin-helmich/prometheus-nginxlog-exporter/exporter:v1`\n\nHave a look at the https://github.com/martin-helmich/prometheus-nginxlog-exporter/releases[releases page]\nto see the available versions and how to pull their images. In general, I would\nrecommend using the `v1` tag instead of `latest`.\n\nRun the exporter as follows (adjust paths like `/path/to/logs` and\n`/path/to/config` to your own needs):\n\n[source]\n----\n$ docker run \\\n --name nginx-exporter \\\n -v /path/to/logs:/mnt/nginxlogs \\\n -p 4040:4040 \\\n quay.io/martinhelmich/prometheus-nginxlog-exporter \\\n mnt/nginxlogs/access.log\n----\n\nCommand-line flags and arguments can simply be appended to the `docker run` command, for example to use a\nconfiguration file:\n\n[source]\n----\n$ docker run \\\n --name nginx-exporter \\\n -p 4040:4040 \\\n -v /path/to/logs:/mnt/nginxlogs \\\n -v /path/to/config.hcl:/etc/prometheus-nginxlog-exporter.hcl \\\n quay.io/martinhelmich/prometheus-nginxlog-exporter \\\n -config-file /etc/prometheus-nginxlog-exporter.hcl\n----\n\n=== DEB and RPM packages\n\nEach https://github.com/martin-helmich/prometheus-nginxlog-exporter/releases[release]\nfrom 1.5.1 or newer provides both DEB and RPM packages.\n\n $ wget https://github.com/martin-helmich/prometheus-nginxlog-exporter/releases/download/v1.6.0/prometheus-nginxlog-exporter_1.6.0_linux_amd64.deb\n $ apt install prometheus-nginxlog-exporter_1.6.0_linux_amd64.deb\n\nThe package come with a dependency on systemd and configure the exporter to be\nrunning automatically:\n\n $ systemctl status prometheus-nginxlog-exporter\n $ # systemctl disable prometheus-nginxlog-exporter\n $ # systemctl enable prometheus-nginxlog-exporter\n\nThe packages drop a configuration file to `/etc/prometheus-nginxlog-exporter.hcl`\nwhich you can adjust to your own needs.\n\n### Manual installation, with systemd\n\nIf you do not want to use one of the pre-built packages, you can download the\nbinary itself and manually configure systemd to start it. You can find an\nexample unit file for this service\nhttps://github.com/martin-helmich/prometheus-nginxlog-exporter/blob/master/res/package/prometheus-nginxlog-exporter.service[in this repository].\nSimply copy the unit file to `/etc/systemd/system`:\n\n $ wget -O /etc/systemd/system/prometheus-nginxlog-exporter.service https://raw.githubusercontent.com/martin-helmich/prometheus-nginxlog-exporter/master/res/package/prometheus-nginxlog-exporter.service\n $ systemctl enable prometheus-nginxlog-exporter\n $ systemctl start prometheus-nginxlog-exporter\n\nThe shipped unit file expects the binary to be located in\n`/usr/sbin/prometheus-nginxlog-exporter` (if you sideload the exporter without\nusing your package manager, you might want to put it to `/usr/local`, instead)\nand the configuration file in `/etc/prometheus-nginxlog-exporter.hcl`. Adjust\nto your own needs.\n\n### Kubernetes\n\nIf you run a logfile-generating service (be it NGINX, or anything that generates\nsimilar access log files) in Kubernetes, you can run the exporter as a sidecar\nalong your \"main\" container within the same pod.\n\nThe following example shows you how to deploy the exporter as a sidecar,\naccepting logs from the main container via syslog:\n\n[source,yaml]\n----\napiVersion: v1\nkind: Pod\nmetadata:\n name: nginx-example\n annotations:\n prometheus.io/scrape: \"true\"\n prometheus.io/port: \"4040\"\nspec:\n containers:\n - name: web\n image: nginx\n # ...\n - name: exporter\n image: docker.pkg.github.com/martin-helmich/prometheus-nginxlog-exporter/exporter:v1\n args: [\"-config-file\", \"/etc/prometheus-nginxlog-exporter/config.hcl\"]\n volumeMounts:\n - name: exporter-config\n mountPath: /etc/prometheus-nginxlog-exporter\n volumes:\n - name: exporter-config\n configMap:\n name: exporter-config\n----\n\nIn this example, the configuration file is passed via the `exporter-config`\nConfigMap. This might look like follows:\n\n[source,yaml]\n----\napiVersion: v1\nkind: ConfigMap\nmetadata:\n name: exporter-config\ndata:\n config.hcl: |\n listen {\n port = 4040\n }\n\n namespace \"nginx\" {\n source = {\n syslog {\n listen_address = \"udp://127.0.0.1:5531\"\n format = \"rfc3164\"\n }\n }\n\n format = \"$remote_addr - $remote_user [$time_local] \\\"$request\\\" $status $body_bytes_sent \\\"$http_referer\\\" \\\"$http_user_agent\\\" \\\"$http_x_forwarded_for\\\"\"\n\n labels {\n app = \"default\"\n }\n }\n----\n\nThe config file instructs the exporter to accept log input via syslog. To\nforward logs to the exporter, just instruct your main container to send its\naccess logs via syslog to `127.0.0.1:5531` (which works, since the main\ncontainer and the sidecar share their network namespace).\n\n### Build from source\n\nTo build the exporter from source, simply build it with `go get`:\n\n $ go get github.com/martin-helmich/prometheus-nginxlog-exporter\n\nAlternatively, clone this repository and just run `go build`:\n\n $ git clone git://github.com/martin-helmich/prometheus-nginxlog-exporter\n $ cd prometheus-nginxlog-exporter\n $ go build\n\n== Collected metrics\n\nThis exporter collects the following metrics. This collector can listen on\nmultiple log files at once and publish metrics in different namespaces. Each\nmetric uses the labels `method` (containing the HTTP request method) and\n`status` (containing the HTTP status code).\n\n[IMPORTANT]\n====\nKeep in mind that some of these metrics will require certain values to be present\nin your access log format (for example, the `http_upstream_time_seconds` metric\nwill require your access to contain the variable `$upstream_response_time`.\n====\n\nMetrics are exported at the `/metrics` path.\n\nThese metrics are exported:\n\n|===\n| `_http_response_count_total` | The total amount of processed HTTP requests/responses.\n| `_http_response_size_bytes` | The total amount of transferred content in bytes.\n| `_http_upstream_time_seconds` | A summary vector of the upstream response times in seconds. Logging these needs to be specifically enabled in NGINX using the `$upstream_response_time` variable in the log format.\n| `_http_upstream_time_seconds_hist` | Same as `_http_upstream_time_seconds`, but as a histogram vector. Also requires the `$upstream_response_time` variable in the log format.\n| `_http_response_time_seconds` | A summary vector of the total response times in seconds. Logging these needs to be specifically enabled in NGINX using the `$request_time` variable in the log format.\n| `_http_response_time_seconds_hist` | Same as `_http_response_time_seconds`, but as a histogram vector. Also requires the `$request_time` variable in the log format.\n|===\n\nAdditional labels can be configured in the configuration file (see below).\n\n`` can be omitted or overridden - see <> for\nmore information.\n\n== Configuration file\n\nYou can specify a configuration file to read at startup. The configuration file\nis expected to be either in https://github.com/hashicorp/hcl[HCL] or YAML format. Here's an example file:\n\n[source,hcl]\n----\nlisten {\n port = 4040\n address = \"10.1.2.3\"\n metrics_endpoint = \"/metrics\"\n}\n\nconsul {\n enable = true\n address = \"localhost:8500\"\n datacenter = \"dc1\"\n scheme = \"http\"\n token = \"\"\n service {\n id = \"nginx-exporter\"\n name = \"nginx-exporter\"\n address = \"192.168.3.1\"\n tags = [\"foo\", \"bar\"]\n }\n}\n\nnamespace \"app1\" {\n format = \"$remote_addr - $remote_user [$time_local] \\\"$request\\\" $status $body_bytes_sent \\\"$http_referer\\\" \\\"$http_user_agent\\\" \\\"$http_x_forwarded_for\\\"\"\n source {\n files = [\n \"/var/log/nginx/app1/access.log\"\n ]\n }\n\n # metrics_override = { prefix = \"myprefix\" }\n # namespace_label = \"vhost\"\n\n labels {\n app = \"application-one\"\n environment = \"production\"\n foo = \"bar\"\n }\n\n histogram_buckets = [.005, .01, .025, .05, .1, .25, .5, 1, 2.5, 5, 10]\n}\n\nnamespace \"app2\" {\n format = \"$remote_addr - $remote_user [$time_local] \\\"$request\\\" $status $body_bytes_sent \\\"$http_referer\\\" \\\"$http_user_agent\\\" \\\"$http_x_forwarded_for\\\" $upstream_response_time\"\n source {\n files = [\n \"/var/log/nginx/app2/access.log\"\n ]\n }\n}\n----\n\nThe same file as YAML file:\n\n[source,yaml]\n----\nlisten:\n port: 4040\n address: \"10.1.2.3\"\n metrics_endpoint: \"/metrics\"\n\nconsul:\n enable: true\n address: \"localhost:8500\"\n datacenter: dc1\n scheme: http\n token: \"\"\n service:\n id: \"nginx-exporter\"\n name: \"nginx-exporter\"\n address = \"192.168.3.1\"\n tags: [\"foo\", \"bar\"]\n\nnamespaces:\n - name: app1\n format: \"$remote_addr - $remote_user [$time_local] \\\"$request\\\" $status $body_bytes_sent \\\"$http_referer\\\" \\\"$http_user_agent\\\" \\\"$http_x_forwarded_for\\\"\"\n source:\n files:\n - /var/log/nginx/app1/access.log\n # metrics_override:\n # prefix: \"myprefix\"\n # namespace_label: \"vhost\"\n labels:\n app: \"application-one\"\n environment: \"production\"\n foo: \"bar\"\n histogram_buckets: [.005, .01, .025, .05, .1, .25, .5, 1, 2.5, 5, 10]\n - name: app2\n format: \"$remote_addr - $remote_user [$time_local] \\\"$request\\\" $status $body_bytes_sent \\\"$http_referer\\\" \\\"$http_user_agent\\\" \\\"$http_x_forwarded_for\\\" $upstream_response_time\"\n source:\n files:\n - /var/log/nginx/app2/access.log\n----\n\nAdvanced features\n-----------------\n### Namespace as labels\n\nFor historic reasons, this exporter exports separate metrics for different\nnamespaces (because the namespace is part of the metric name). However, in many\n(most) cases, it's more convenient to have the same metric name across different\nnamespaces (with different log formats and names).\n\nThis can be done in two steps:\n\n1. Override Prometheus metrics namespace to some common prefix (`metrics_override`)\n2. Set label name for nginxlog-exporter's config namespace (`namespace_label`)\n\n[source,hcl]\n----\nnamespace \"app1\" {\n ...\n metrics_override = { prefix = \"myprefix\" }\n namespace_label = \"vhost\"\n ...\n}\n\nnamespace \"app2\" {\n ...\n metrics_override = { prefix = \"myprefix\" }\n namespace_label = \"vhost\"\n ...\n}\n----\n\nExported metrics will have the following format:\n[source]\n----\nmyprefix_http_response_count_total{vhost=\"app1\", ...}\nmyprefix_http_response_count_total{vhost=\"app2\", ...}\n...\n----\n\n* `prefix` can be set to `\"\"`, resulting metrics like `http_response_count_total{...}`\n* `namespace_label` can be omitted - so you have full control on metric format\n\nSome details and history on this can be found in https://github.com/martin-helmich/prometheus-nginxlog-exporter/issues/13[issue #13].\n\n### Custom labels pass-through\n\nPartial case of <>:\n\n[source,hcl]\n----\nnamespace \"app1\" {\n format = \"$remote_addr - $remote_user [$time_local] ... \\\"$geoip_country_code\\\" $upstream_addr\"\n ...\n relabel \"upstream_addr\" { from = \"upstream_addr\" }\n relabel \"country\" { from = \"geoip_country_code\" }\n ...\n}\n----\n\nExported metrics will have `upstream_addr` and `country` labels.\n\n### Log sources\n\nCurrently, the exporter supports reading log data from\n\n1. files\n2. syslog\n\nAll log sources can be configured on a per-namespace basis using the `source` property.\n\n#### Reading from files\n\nWhen reading from log files, all that is needed is a `files` property:\n\n```hcl\nnamespace \"test\" {\n source {\n files = [\"/var/log/nginx/access.log\"]\n // ...\n }\n}\n```\n\n#### Reading from syslog\n\nThe exporter can also open and listen on a Syslog port and read logs from there. Configuration works as follows:\n\n[source,hcl]\n----\nnamespace \"test\" {\n source {\n syslog {\n listen_address = \"udp://127.0.0.1:8514\" <1>\n format = \"rfc3164\" <2>\n tags = [\"nginx\"]\n }\n\n // ...\n }\n}\n----\n<1> The `listen_address` might be either a TCP or UDP address. UNIX sockets are not supported (yet -- pull requests are welcome)\n<2> The `format` may be one of `rfc3164`, `rfc5424`, `rfc6587` or `auto`. If omitted, it will default to `auto`.\n\nHave a look at http://nginx.org/en/docs/syslog.html[the respective section of the NGINX documentation] on how to set up NGINX to log into syslog.\n\nExperimental features\n---------------------\n\nThe exporter contains features that are currently experimental and may change without prior notice.\nTo use these features, either set the `-enable-experimental` flag or add a `enable_experimental`\noption to your configuration file (on the root of the configuration file document, like\n`enable_experimental: true` in YAML or `enable_experimental = true` in HCL).\n\n### Dynamic re-labeling\n\nRe-labeling lets you add arbitrary fields from the parsed log line as labels to your metrics.\nTo add a dynamic label, add a `relabel` statement to your configuration file:\n\n[source,hcl]\n----\nnamespace \"app-1\" {\n // ...\n\n relabel \"host\" {\n from = \"server_name\"\n whitelist = [ <1>\n \"host-a.com\",\n \"host-b.de\"\n ]\n }\n}\n----\n<1> The `whitelist` property is optional; if set, only the supplied values will be added as label.\nAll other values will be subsumed under the `\"other\"` label value. See #16 for a more detailed\ndiscussion around the reasoning.\n\nDynamic relabeling also allows you to aggregate your metrics by request path (which replaces\nthe experimental feature originally introduced in #23). The following example splits the content of\nthe `request` variable at every space (using `split`) and return the second element (index 1) of the\nresulting list which is the base for the regex):\n\n[source,hcl]\n----\nnamespace \"app1\" {\n // ...\n\n relabel \"request_uri\" {\n from = \"request\"\n split = 2\n\n match \"^/users/[0-9]+\" {\n replacement = \"/users/:id\"\n }\n\n match \"^/profile\" {\n replacement = \"/profile\"\n }\n }\n}\n----\n\nIf a match is found, the `replacement` replaces each occurrence of the corresponding match in the original value. Otherwise the processing continues to check the following match statements.\n\nThe YAML configuration for relabelings works similar to the HCL configuration:\n\n[source,yaml]\n----\nnamespaces:\n- name: app1\n relabel_configs:\n - target_label: request_uri\n from: request\n split: 2\n matches:\n - regexp: \"^/users/[0-9]+\"\n replacement: \"/users/:id\"\n----\n\nIf your regular expression contains groups, you can also use the matched values of those in the `replacement` value:\n\n[source,hcl]\n----\nrelabel \"request_uri\" {\n from = \"request\"\n split = 2\n \n match \"^/(users|profiles)/[0-9]+\" {\n replacement = \"/$1/:id\"\n }\n}\n----\n\n### Reading from Docker logs\n\nIf Nginx is running in a docker container and is configured to log to `/dev/stdout` and `/dev/stderr` (this is the\ndefault configuration of the official `nginx` image), then you can export logs using Docker's default logging driver.\nTo do this use a source configuration as follows:\n\n[source,hcl]\n----\nnamespace \"test\" {\n source {\n docker {\n container = \"nginx_container_name\"\n }\n\n // ...\n }\n}\n----\n\nThe host's docker socket needs to be mounted to the container. For example, if using the docker run command as follows:\n\n[source]\n----\n$ docker run \\\n --name nginx-exporter \\\n -v /var/run/docker.sock:/var/run/docker.sock \\\n -v /path/to/config.hcl:/etc/prometheus-nginxlog-exporter.hcl \\\n -p 4040:4040 \\\n quay.io/martinhelmich/prometheus-nginxlog-exporter \\\n -config-file /etc/prometheus-nginxlog-exporter.hcl \\\n -enable-experimental\n----\n\n== Frequently Asked Questions\n\n> I have started the exporter, but it is not exporting any application-specific metrics!\n\nThis may have several issues:\n\n1. Make sure that the access log files that your exporter is listening on are present. The exporter will exit with an error code if a file is present but cannot be opened (for example, due to bad permissions), but will _wait_ for a file if it does not yet exist.\n2. Make sure that the exporter can parse the lines from your access log files. Pay attention to the `_parse_errors_total` metric, which will indicate how many log lines could not be parsed.\n\n> The exporter exports the `_http_response_count_total` metric, but not _[other metric that is mentioned in the README]_!\n\nMost metrics require certain values to be present in the access log files that are not present in the NGINX default configuration. Especially, make sure that the access log contains the http://nginx.org/en/docs/http/ngx_http_upstream_module.html#var_upstream_response_time[`$upstream_response_time`], http://nginx.org/en/docs/http/ngx_http_log_module.html#var_request_time[`$request_time`] and/or http://nginx.org/en/docs/http/ngx_http_core_module.html#variables[`$body_bytes_sent`] variables. These need to be enabled in the NGINX configuration (more precisely, the `log_format` setting) and then added to the format specified for the exporter.\n\n> How can I configure NGINX to export these variables?\n\nHave a look at NGINX's https://www.nginx.com/resources/admin-guide/logging-and-monitoring/[Logging and Monitoring] guide. It contains some good examples that contain the `$request_time` and `$upstream_response_time`:\n\n```\nlog_format upstream_time '$remote_addr - $remote_user [$time_local] '\n '\"$request\" $status $body_bytes_sent '\n '\"$http_referer\" \"$http_user_agent\"'\n 'rt=$request_time uct=\"$upstream_connect_time\" uht=\"$upstream_header_time\" urt=\"$upstream_response_time\"';\n```\n\nCredits\n-------\n\n- https://github.com/hpcloud/tail[tail], MIT license\n- https://github.com/satyrius/gonx[gonx], MIT license\n- https://github.com/prometheus/client_golang[Prometheus Go client library], Apache License\n- https://github.com/hashicorp/hcl[HashiCorp configuration language], Mozilla Public License\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",7601220,"orgData",{"_86":87,"_88":89,"_90":91,"_92":29,"_93":94,"_95":96,"_97":94,"_98":99,"_100":101,"_102":103,"_104":44,"_105":44,"_106":17},"id","40722f9e74c011e4bea40242ac11001b","uuid","40722f9e-74c0-11e4-bea4-0242ac11001b","type","organization","orgname","full_name","The Texas Tribune","location","Austin, TX","company","profile_url","http://texastribune.org/","date_joined","2014-06-12T21:25:42.962947Z","gravatar_url","https://www.gravatar.com/avatar/453224f593817ff219630558ba37b856?s=80&r=g&d=mm","gravatar_email","badge","is_active","recentTags",[109],{"_110":40,"_111":112,"_113":114,"_86":115,"_116":117,"_46":134,"_135":112,"_136":29,"_137":52,"_53":138,"_139":140,"_141":125,"_142":134,"_143":62,"_144":17},"content_type","creator",33196,"full_size",7598907,99961532,"images",[118],{"_119":120,"_121":122,"_123":44,"_124":125,"_126":127,"_128":129,"_130":44,"_131":-5,"_132":114,"_59":62,"_133":-5},"architecture","amd64","digest","sha256:bcb41d7c00999ffb9bf50dffe686bd658f78c9d26675ced7f64cf189ddc08e35","features","last_pulled","2026-09-14T12:48:33.422775694Z","last_pushed","2020-05-12T15:57:29Z","os","linux","os_features","os_version","size","variant","2020-05-12T15:57:28.591287Z","last_updater","last_updater_username","media_type","latest","repository",9023896,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":154,"_161":162,"_150":171,"_172":11},{"_36":155,"_38":156,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":157,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":158,"_75":11,"_76":160,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":159},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_163":60,"_164":-5,"_165":-5,"_166":167},"count","next","previous","results",[168],{"_110":40,"_111":112,"_113":114,"_86":115,"_116":169,"_46":134,"_135":112,"_136":29,"_137":52,"_53":138,"_139":140,"_141":125,"_142":134,"_143":62,"_144":17},[170],{"_119":120,"_121":122,"_123":44,"_124":125,"_126":127,"_128":129,"_130":44,"_131":-5,"_132":114,"_59":62,"_133":-5},[],"canDeleteTags","actionData","errors"]

texastribune/prometheus-nginxlog-exporter

Tags for texastribune/prometheus-nginxlog-exporter