theme | highlightTheme |
---|---|
night |
monokai |
2021-07-25T04:12:50Z INFO handling request
2021-07-25T04:12:50Z INFO handling request
2021-07-25T04:12:50Z INFO authorizing "123"
2021-07-25T04:12:50Z INFO authorizing "543"
2021-07-25T04:12:51Z INFO authorized
2021-07-25T04:12:52Z INFO unauthorized
$100B industry to handle this! 💸🔥
{
"time": "2021-07-25T04:12:50Z",
"msg": "authorized"
}
Structure means we can parse it with a broad range of tools.
{
"time": "2021-07-25T04:12:50Z",
"msg": "authorized",
"id": "123"
}
Context means why can ask more interesting questions.
"how frequently does this ID authenticate with success?"
{
"time": "2021-07-25T04:12:50Z",
"msg": "authorized",
"id": "123",
"groups": ["a", "b"]
}
Ephemeral state is particularly hard to troubleshoot.
{
"time": "2021-07-25T04:12:50Z",
"application": "authorizer@3.0.1",
"msg": "authorized",
"id": "123",
"groups": ["a", "b"]
}
System context means we know what emitting this; and which version.
"when did this start failing? is this a bug with v3?"
{
"time": "2021-07-25T04:12:50Z",
"application": "authorizer@3.0.1",
"msg": "authorized",
"id": "123",
"groups": ["a", "b"],
"cache_used": "1627186370"
}
System state is often ephemeral; in-memory only; perilous.
{
"time": "2021-07-25T04:12:50Z",
"application": "authorizer@3.0.1",
"msg": "authorized",
"id": "123",
"groups": ["a", "b"],
"cache_used": "1627186370",
"request_id": "a39b28c9"
}
A complex system may emit many events; a request ID brings lineage.
{
"time": "2021-07-25T04:12:50Z",
"application": "authorizer@3.0.1",
"msg": "authorized",
"id": "123",
"groups": ["a", "b"],
"cache_used": "1627186370",
"request_id": "a39b28c9",
"corelation_id": "d4289bd7"
}
A distributed system add more complexity; consider a specialized ID to across system boundaries.