We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When pointing to own Elasticsearch server using "LOG_RECEIVER_URL" (or command-line flag), you should be able to specify your own index, but the Heroku listener seems to try to enforce that the index matches a regex here: https://github.com/sematext/logagent-js/blob/master/lib/plugins/input/heroku.js#L81
It prints the error: Error: Missing Logsene Token /asdf. Please use /LOGSENE_TOKEN.
Error: Missing Logsene Token /asdf. Please use /LOGSENE_TOKEN.
I would like "https://myserver.herokuapp.com/asdf" to work without it having to be in the UUID format like a Sematext/Logscene token.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When pointing to own Elasticsearch server using "LOG_RECEIVER_URL" (or command-line flag), you should be able to specify your own index, but the Heroku listener seems to try to enforce that the index matches a regex here:
https://github.com/sematext/logagent-js/blob/master/lib/plugins/input/heroku.js#L81
It prints the error:
Error: Missing Logsene Token /asdf. Please use /LOGSENE_TOKEN.I would like "https://myserver.herokuapp.com/asdf" to work without it having to be in the UUID format like a Sematext/Logscene token.
The text was updated successfully, but these errors were encountered: