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

Secondary configuration not supported #10

Open
sahilsareen opened this issue May 6, 2016 · 0 comments
Open

Secondary configuration not supported #10

sahilsareen opened this issue May 6, 2016 · 0 comments

Comments

@sahilsareen
Copy link

Configuration:

<match http_source>
  type sns
  sns_topic_name XX
  aws_key_id XX
  aws_sec_key XX
  sns_endpoint XX

  <secondary>
    type file
    path /var/log/td-agent/failed_events_http_source
  </secondary>
</match>

# Accept events from HTTP source at http://SOMEURL:8827/http_source/<JSON EVENT>
<source>
  type http
  port 8827
</source>

Steps to reproduce:

  1. Do the above configuration
  2. Start HTTP traffic
  3. Delete the SNS topic

Expectation:
Events should now be appended to /var/log/td-agent/failed_events_http_source

Outcome:
On console:

500 Internal Server Error
Topic does not exist

Reference: http://docs.fluentd.org/articles/buffer-plugin-overview#secondary-output

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

No branches or pull requests

1 participant