Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong Organization/Event-ID parsing for nginx access log #17

Open
Hufschmidt opened this issue Nov 9, 2020 · 1 comment · May be fixed by #19
Open

Wrong Organization/Event-ID parsing for nginx access log #17

Hufschmidt opened this issue Nov 9, 2020 · 1 comment · May be fixed by #19

Comments

@Hufschmidt
Copy link

Hufschmidt commented Nov 9, 2020

With access-logs generated by our nginx frontend we get the following access-log entries:

<remote> - - [<time>] "GET /static/<org>/api/<event>/<video>.mp4?policy=<...>&keyId=<org>&signature=<...> ..."

while the current parser seems to require

<remote> - - [<time>] "GET /<org>/api/<event>/<video>.mp4?policy=<...>&keyId=<org>&signature=<...> ..."

(without /static prefix)

This leads to invalid detection of <org> and <event> fields and those causes the opencast-influxdb-db adapter to exit when requesting information for org=static, event=api since those do not exists.

Possible solution: Configurable url-prefix (default: /)

@hsssystems
Copy link

Hi,

we already made a patch for this that allows you to configure the regular expression and parse the logs. We are working on a Pull Request.

@berthob98 berthob98 linked a pull request Jan 15, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants