SisMaker
/
lager
1
0
Çatalla 0
Kod Konular 0 Değişiklik İstekleri 0 Projeler 0 Sürümler 53 Wiki Aktivite
25'ten fazla konu seçemezsiniz Konular bir harf veya rakamla başlamalı, kısa çizgiler ('-') içerebilir ve en fazla 35 karakter uzunluğunda olabilir.
638 İşleme
4 Dallar
2.4 MiB
Ağaç: 6452db6388
Dallar Biçim İmleri
${ item.name }
${ searchTerm } dalı oluştur
'6452db6388'den
${ noResults }
lager/src/lager_msg.erl

64 satır
1.8 KiB
Ham Normal Görünüm Geçmiş

Use an opaque type with a module for accessors rather than a record I didn't want the lager_log_message record being used across application boundaries, this will insulate other applications from any changes to the message type's internal structure.
12 yıl önce
​
Improve the performance of the file backend This is done via a combination of several things: * Make the loglevel that triggers a sync configurable * Make the delayed_write size and intervals configurable * Make the interval at which external rotation is checked for configurable * Store the timestamp a lager_msg was created inside the lager_msg To support these changes, several other things had to be modified: * lager_msg:timestamp now returns a timestamp * lager_msg:datetime was added to return the {date, time} of a message, like lager_msg:timestamp used to * The configuration syntax for file backends was changed to be of the form {lager_file_backend, proplist()} and the old syntax was deprecated Additionally, the defaults for the check_interval was raised from 'always' to 1 second, and the sync_interval was changed from 2 seconds to one second.
12 yıl önce
Use an opaque type with a module for accessors rather than a record I didn't want the lager_log_message record being used across application boundaries, this will insulate other applications from any changes to the message type's internal structure.
12 yıl önce
​
Improve the performance of the file backend This is done via a combination of several things: * Make the loglevel that triggers a sync configurable * Make the delayed_write size and intervals configurable * Make the interval at which external rotation is checked for configurable * Store the timestamp a lager_msg was created inside the lager_msg To support these changes, several other things had to be modified: * lager_msg:timestamp now returns a timestamp * lager_msg:datetime was added to return the {date, time} of a message, like lager_msg:timestamp used to * The configuration syntax for file backends was changed to be of the form {lager_file_backend, proplist()} and the old syntax was deprecated Additionally, the defaults for the check_interval was raised from 'always' to 1 second, and the sync_interval was changed from 2 seconds to one second.
12 yıl önce
Use an opaque type with a module for accessors rather than a record I didn't want the lager_log_message record being used across application boundaries, this will insulate other applications from any changes to the message type's internal structure.
12 yıl önce
​
​
​
​
​
​
​
​
Improve the performance of the file backend This is done via a combination of several things: * Make the loglevel that triggers a sync configurable * Make the delayed_write size and intervals configurable * Make the interval at which external rotation is checked for configurable * Store the timestamp a lager_msg was created inside the lager_msg To support these changes, several other things had to be modified: * lager_msg:timestamp now returns a timestamp * lager_msg:datetime was added to return the {date, time} of a message, like lager_msg:timestamp used to * The configuration syntax for file backends was changed to be of the form {lager_file_backend, proplist()} and the old syntax was deprecated Additionally, the defaults for the check_interval was raised from 'always' to 1 second, and the sync_interval was changed from 2 seconds to one second.
12 yıl önce
Fix typespecs for a clean dialyzer run Fix typespec of lager_file_backend:init() and lager_msg record
12 yıl önce
Use an opaque type with a module for accessors rather than a record I didn't want the lager_log_message record being used across application boundaries, this will insulate other applications from any changes to the message type's internal structure.
12 yıl önce
​
​
​
​
​
Improve the performance of the file backend This is done via a combination of several things: * Make the loglevel that triggers a sync configurable * Make the delayed_write size and intervals configurable * Make the interval at which external rotation is checked for configurable * Store the timestamp a lager_msg was created inside the lager_msg To support these changes, several other things had to be modified: * lager_msg:timestamp now returns a timestamp * lager_msg:datetime was added to return the {date, time} of a message, like lager_msg:timestamp used to * The configuration syntax for file backends was changed to be of the form {lager_file_backend, proplist()} and the old syntax was deprecated Additionally, the defaults for the check_interval was raised from 'always' to 1 second, and the sync_interval was changed from 2 seconds to one second.
12 yıl önce
​
Use an opaque type with a module for accessors rather than a record I didn't want the lager_log_message record being used across application boundaries, this will insulate other applications from any changes to the message type's internal structure.
12 yıl önce
Improve the performance of the file backend This is done via a combination of several things: * Make the loglevel that triggers a sync configurable * Make the delayed_write size and intervals configurable * Make the interval at which external rotation is checked for configurable * Store the timestamp a lager_msg was created inside the lager_msg To support these changes, several other things had to be modified: * lager_msg:timestamp now returns a timestamp * lager_msg:datetime was added to return the {date, time} of a message, like lager_msg:timestamp used to * The configuration syntax for file backends was changed to be of the form {lager_file_backend, proplist()} and the old syntax was deprecated Additionally, the defaults for the check_interval was raised from 'always' to 1 second, and the sync_interval was changed from 2 seconds to one second.
12 yıl önce
​
Use an opaque type with a module for accessors rather than a record I didn't want the lager_log_message record being used across application boundaries, this will insulate other applications from any changes to the message type's internal structure.
12 yıl önce
​
Improve the performance of the file backend This is done via a combination of several things: * Make the loglevel that triggers a sync configurable * Make the delayed_write size and intervals configurable * Make the interval at which external rotation is checked for configurable * Store the timestamp a lager_msg was created inside the lager_msg To support these changes, several other things had to be modified: * lager_msg:timestamp now returns a timestamp * lager_msg:datetime was added to return the {date, time} of a message, like lager_msg:timestamp used to * The configuration syntax for file backends was changed to be of the form {lager_file_backend, proplist()} and the old syntax was deprecated Additionally, the defaults for the check_interval was raised from 'always' to 1 second, and the sync_interval was changed from 2 seconds to one second.
12 yıl önce
​
​
​
​
Use an opaque type with a module for accessors rather than a record I didn't want the lager_log_message record being used across application boundaries, this will insulate other applications from any changes to the message type's internal structure.
12 yıl önce
​
​
​
Fix typespecs for a clean dialyzer run Fix typespec of lager_file_backend:init() and lager_msg record
12 yıl önce
Use an opaque type with a module for accessors rather than a record I didn't want the lager_log_message record being used across application boundaries, this will insulate other applications from any changes to the message type's internal structure.
12 yıl önce
​
​
Fix typespecs for a clean dialyzer run Fix typespec of lager_file_backend:init() and lager_msg record
12 yıl önce
Improve the performance of the file backend This is done via a combination of several things: * Make the loglevel that triggers a sync configurable * Make the delayed_write size and intervals configurable * Make the interval at which external rotation is checked for configurable * Store the timestamp a lager_msg was created inside the lager_msg To support these changes, several other things had to be modified: * lager_msg:timestamp now returns a timestamp * lager_msg:datetime was added to return the {date, time} of a message, like lager_msg:timestamp used to * The configuration syntax for file backends was changed to be of the form {lager_file_backend, proplist()} and the old syntax was deprecated Additionally, the defaults for the check_interval was raised from 'always' to 1 second, and the sync_interval was changed from 2 seconds to one second.
12 yıl önce
​
​
Use an opaque type with a module for accessors rather than a record I didn't want the lager_log_message record being used across application boundaries, this will insulate other applications from any changes to the message type's internal structure.
12 yıl önce
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
 
  1. -module(lager_msg).
  2. 

  3. -export([new/4, new/5]).
  4. -export([message/1]).
  5. -export([timestamp/1]).
  6. -export([datetime/1]).
  7. -export([severity/1]).
  8. -export([severity_as_int/1]).
  9. -export([metadata/1]).
  10. -export([destinations/1]).
  11. 

  12. -record(lager_msg,{
  13.         destinations :: list(),
  14.         metadata :: [tuple()],
  15.         severity :: lager:log_level(),
  16.         datetime :: {string(), string()},
  17.         timestamp :: erlang:timestamp(),
  18.         message :: list()
  19.     }).
  20. 

  21. -opaque lager_msg() :: #lager_msg{}.
  22. -export_type([lager_msg/0]).
  23. 

  24. %% create with provided timestamp, handy for testing mostly

  25. -spec new(list(), erlang:timestamp(), lager:log_level(), [tuple()], list()) -> lager_msg().
  26. new(Msg, Timestamp, Severity, Metadata, Destinations) ->
  27.     {Date, Time} = lager_util:format_time(lager_util:maybe_utc(lager_util:localtime_ms(Timestamp))),
  28.     #lager_msg{message=Msg, datetime={Date, Time}, timestamp=Timestamp, severity=Severity,
  29.         metadata=Metadata, destinations=Destinations}.
  30. 

  31. -spec new(list(), lager:log_level(), [tuple()], list()) -> lager_msg().
  32. new(Msg, Severity, Metadata, Destinations) ->
  33.     Now = os:timestamp(),
  34.     new(Msg, Now, Severity, Metadata, Destinations).
  35. 

  36. -spec message(lager_msg()) -> list().
  37. message(Msg) ->
  38.     Msg#lager_msg.message.
  39. 

  40. -spec timestamp(lager_msg()) -> erlang:timestamp().
  41. timestamp(Msg) ->
  42.     Msg#lager_msg.timestamp.
  43. 

  44. -spec datetime(lager_msg()) -> {string(), string()}.
  45. datetime(Msg) ->
  46.     Msg#lager_msg.datetime.
  47. 

  48. -spec severity(lager_msg()) -> lager:log_level().
  49. severity(Msg) ->
  50.     Msg#lager_msg.severity.
  51. 

  52. -spec severity_as_int(lager_msg()) -> lager:log_level_number().
  53. severity_as_int(Msg) ->
  54.     lager_util:level_to_num(Msg#lager_msg.severity).
  55. 

  56. -spec metadata(lager_msg()) -> [tuple()].
  57. metadata(Msg) ->
  58.     Msg#lager_msg.metadata.
  59. 

  60. -spec destinations(lager_msg()) -> list().
  61. destinations(Msg) ->
  62.     Msg#lager_msg.destinations.
  63. 

  64.