Customers periodically ask "Why am I getting errors when talking to Redis". The answer is complicated - it could be a client or server side problem. In this article, I am going to talk about client side issues. For server side issues, see here
Clients can see connectivity issues or timeouts for several reason, here are some of the common ones I see:
###Memory pressure
| namespace Analogy | |
| { | |
| /// <summary> | |
| /// This example shows that a library that needs access to target .NET Standard 1.3 | |
| /// can only access APIs available in that .NET Standard. Even though similar the APIs exist on .NET | |
| /// Framework 4.5, it implements a version of .NET Standard that isn't compatible with the library. | |
| /// </summary>INetCoreApp10 | |
| class Example1 | |
| { | |
| public void Net45Application(INetFramework45 platform) |
It's very easy for remote working to fail if the company doesn't invest in it. It requires buy-in from the entire company, but the benefits are significant:
| # In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env | |
| # variable pointing GPG to the gpg-agent socket. This little script, which must be sourced | |
| # in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start | |
| # gpg-agent or set up the GPG_AGENT_INFO variable if it's already running. | |
| # Add the following to your shell init to set up gpg-agent automatically for every shell | |
| if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then | |
| source ~/.gnupg/.gpg-agent-info | |
| export GPG_AGENT_INFO | |
| else |
Exceptionless Contributor License Agreement
The document below clarifies the terms under which You (the copyright owner or legal entity authorized by the copyright owner), may make “The Contributions” (software, bug fixes, configuration changes, documentation, or any other materials) to “The Work” (Exceptionless/Exceptionless). This license protects You, “The Company” (Exceptionless) and licensees; it does not change your rights to use your own contributions for any other purpose.
Please complete the following information about You and The Contributions. If you have questions about these terms, please contact us at team@exceptionless.com.
You and “The Company” (Exceptionless) agree:
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>Untitled</title> | |
| <link rel="stylesheet" href="http://kendo.cdn.telerik.com/2015.3.930/styles/kendo.common.min.css"> | |
| <link rel="stylesheet" href="http://kendo.cdn.telerik.com/2015.3.930/styles/kendo.rtl.min.css"> | |
| <link rel="stylesheet" href="http://kendo.cdn.telerik.com/2015.3.930/styles/kendo.default.min.css"> | |
| <link rel="stylesheet" href="http://kendo.cdn.telerik.com/2015.3.930/styles/kendo.mobile.all.min.css"> |
| apt-get install nodejs | |
| apt-get install npm | |
| cd /opt | |
| git clone https://github.com/etsy/statsd.git | |
| npm install -g forerver | |
| cd statsd | |
| nano config.js and copy the config file below | |
| npm install statsd-librato-backend | |
| apt-get install upstart monit | |
| nano /etc/init/statsd.conf ( http://zzarbi.tumblr.com/post/43762180430/statsd-and-ubuntu-server-12-10) |
| // Override the default submission client | |
| public class ProxySubmissionClient : SubmissionClient { | |
| protected override HttpWebRequest CreateHttpWebRequest(ExceptionlessConfiguration config, string endPoint) { | |
| var request = base.CreateHttpWebRequest(config, endPoint); | |
| // Set the proxy info here. | |
| try { | |
| request.Proxy = new WebProxy("MyProxyAddress"); | |
| } catch (Exception) {} |
| function plugin1(context, next) { | |
| console.log('plugin1'); | |
| console.log(context.event); | |
| next(); | |
| } | |
| function plugin2(context, next) { | |
| console.log('plugin2'); | |
| someIO(next); | |
| } |
| // I'm working on the client api for submitting log messages, feature usages and exceptions to https://github.com/exceptionless/Exceptionless.. | |
| // Please leave a comment with what you like or what you prefer. | |
| // ------ log messages ----- | |
| //Considerations: only message param is required. | |
| // I like this as it feels native to js, but I don't like that source is the first, | |
| // when it could be inferred if not set.. You could find yourself doing client.log(null, message) all over.. | |
| client.log(source, message, level); |
