Skip to content
This repository
branch: master

Jul 10, 2014

  1. Alex Arnell

    Merge pull request #91 from heroku/firehose-spike

    Add a firehose channel
    voidlock authored

Jul 09, 2014

  1. Alex Arnell

    add a firehose channel

    The firehose will syphon off select messages and submit those messages
    to a pool of available firehose channels. This allows for subset of logs
    to be redirected down a known smaller group of channels.
    
    The firehose is controlled via two environment variables
    `FIREHOSE_CHANNEL_IDS` and `FIREHOSE_FILTER_TOKENS`. Both are comma
    separated lists. The former is a list the list of channels the firehose
    will use. The latter is a list of interested app token names that should
    be filtered down the firehose.
    ```
    FIREHOSE_CHANNEL_IDS="1000,1100,1200"
    FIREHOSE_FILTER_TOKENS="events,metrics"
    ```
    The above variables would filter all "events" and "metrics" log messages
    down the firehose. The firehose itself will shard logs across three
    channels, 1000, 1100, and 1200 using random distribution.
    
    The firehose can be disabled at runtime by simply calling
    ```erlang
    logplex_firehose:disable().
    ```
    
    Once disabled the firehose can be enabled again by using
    ```erlang
    logplex_firehose:enable().
    ```
    This allows for dynamic reconfiguration of the firehose by modifing the
    logplex application env variables at runtime. Those variables are
    lowercase versions of the OS environment variables
    `firehose_channel_ids` and `firehose_filter_tokens` respectively.
    voidlock authored Alex Arnell committed

Jul 01, 2014

  1. Alex Arnell

    Merge pull request #94 from heroku/travis-update

    new team owner new reporting channel
    voidlock authored
  2. new team owner new reporting channel

    Alex Arnell authored

Mar 27, 2014

  1. Phil Hagelberg

    Clarify that it's just the caching that's disabled.

    technomancy authored
  2. Phil Hagelberg

    Disable logplex_stats's caching of its ets table.

    This gen_server is currently consuming the most memory of all
    processes in production by a fairly large margin.
    technomancy authored

Mar 18, 2014

  1. fix hipchat config

    Tristan Sloughter authored
  2. build with public rebar config and then build test config

    Tristan Sloughter authored
  3. add skip deps for travis

    Tristan Sloughter authored
  4. Phil Hagelberg

    Add live_upgrade file for v72.

    technomancy authored
  5. Phil Hagelberg

    Merge branch 'nosuspend-port-buffer'

    technomancy authored
  6. use public redgrid in test rebar config

    Tristan Sloughter authored
  7. add travis-ci config

    Tristan Sloughter authored
  8. Phil Hagelberg

    Increment drain_dropped when tcp drain port buffer is full.

    technomancy authored
  9. Phil Hagelberg

    Start send timer after we know the send has succeeded.

    Rather than starting and stopping it.
    technomancy authored
  10. Phil Hagelberg

    Don't increment drain_delivered on port failure.

    Also head to ready_to_send state instead of sending.
    technomancy authored
  11. Phil Hagelberg

    Log when port_command fails due to a busy port.

    technomancy authored

Mar 17, 2014

  1. Phil Hagelberg

    Don't suspend process when we push data to a full buffer.

    We're seeing instances in production where TCP incast can cause
    processes to be descheduled, resulting in mailboxes backing up and
    running out of memory.
    
    http://www.snookles.com/slf-blog/2012/01/05/tcp-incast-what-is-it/
    
    In cases where this happens it's better to just take a hit and drop
    the data than to risk letting the mailbox back up.
    technomancy authored
  2. Phil Hagelberg

    Make tail warning header consistent with other API endpoints.

    technomancy authored

Mar 14, 2014

  1. Fred Hebert

    Merge pull request #86 from kiyoto/patch-1

    Wrong RFC number referenced?
    ferd authored
  2. Kiyoto

    Wrong RFC number referenced?

    kiyoto authored

Mar 06, 2014

  1. Phil Hagelberg

    Merge pull request #85 from heroku/log-history-warning

    Log history warning
    technomancy authored

Mar 05, 2014

  1. Phil Hagelberg

    Revert "Replace no_tail_warning with generalized format_warning."

    This reverts commit 8ace66c.
    
    We don't actually want that formatting for HTTP headers.
    technomancy authored
  2. Phil Hagelberg

    Use format_warning for no_redis tails.

    technomancy authored

Mar 04, 2014

  1. Phil Hagelberg

    Replace no_tail_warning with generalized format_warning.

    technomancy authored
  2. Phil Hagelberg

    Turns out lookup_flag returns the flag, not true/false.

    technomancy authored
  3. Phil Hagelberg

    Include "Log-History: none" header when no_redis flag is set.

    This will allow the toolbelt to warn users when their apps get flagged
    in for excessive output volume.
    technomancy authored

Feb 28, 2014

  1. Phil Hagelberg

    Stick with bin/ scripts over makefile.

    technomancy authored

Feb 26, 2014

  1. Phil Hagelberg

    Merge pull request #84 from eiri/makefile-and-missing-config

    Added Makefile and missing config file
    technomancy authored
  2. Eiri

    Added Makefile and missing config file; Removed obsolete include from…

    … uuid.erl
    eiri authored

Feb 08, 2014

  1. Geoff Cant

    Merge pull request #83 from nolman/master

    use canonical repository link
    archaelus authored
  2. Nolan Evans

    use canonical repository link

    nolman authored

Feb 03, 2014

  1. Phil Hagelberg

    Allow bin/devel_logplex to see .hrl files.

    So it can be used for, you know, development.
    technomancy authored

Jan 22, 2014

  1. Phil Hagelberg

    Merge branch 'close-active-drains'

    # Please enter a commit message to explain why this merge is necessary,
    # especially if it merges an updated upstream into a topic branch.
    #
    # Lines starting with '#' will be ignored, and an empty message aborts
    # the commit.
    technomancy authored
  2. Phil Hagelberg

    Add live_upgrade.erl for v70.1 -> v71.

    technomancy authored
Something went wrong with that request. Please try again.