The current godoc says of Logger.Out:

It's common to set this to a file, or leave it default which is os.Stderr.

However, this is in the struct doc rather than the documentation for logrus.New. The default when declaring a logrus.Logger as a struct is, of course, nil, and leaving it that way results in a panic [whenever a log wou

the above is a usually appeared screen-shot in jupyter notebook, if colored in columns, it would be really helpful to distinguish time/line number/code/variables parts.

Some files in the repository are missing newlines at the very end, as pointed out by @nrbrook in #1026

Classes/CocoaLumberjack.h was specifically mentioned, but there could be other files that are missing this as well.

Doc changes:

• Rework security docs (WIP)
  • API key docs (with Colin)
  • Doc:Add section to security docs for API key information #11974
  • Doc:Add info on using api keys for access #11990
• Cloud First work ([Meta issue #11530](https://github.com/elastic/logstash

Now, this could be a controversial one, because of the added ambiguity.

There is no way to indicate that an entry has been sampled because of the very definition of sampling. But what can be done is a boolean field added to the n-th (where n = first) and every subsequent entry within one tick. Let's call it sampling_threshold_reached for the lack of better name.

This could be helpf

Is your feature request related to a problem? Please describe.

We plan to do ruling and alerting like Prom with Alertmanager, but in the meantime we have multiple ways to already alerts on logs and I think we should document it.

This include alerting with Promtail/Alertmanager using stages or alerting with Grafana using Loki as Prometheus datasource.

We should also explain that you

@repeatedly , In #1856 issue, I'm very happy to see you add a nice feature to backup for bad chunk. In our production environment, I found it works. But when I check the bad chunk I don't know what tag is it. So I suggest also save the meta information. It is useful for check and repair data.

I am trying to run an express app through Visual Studio Code. I have a launch.json file with DEBUG defined like so:

        "env": {
             "DEBUG": "*"
        }

Here is a trimmed down version of my app.js file where you can see the bolded debug line that doesn't output to the debug console (Test 2). Test 1 before it outputs as expected. If I run this from the command li

This stackoverflow post outlines a different method of using namedParameters than the readme and seems to be correct. Readme could be updated to match.

https://stackoverflow.com/questions/6212219/passing-parameters-to-a-bash-function

The documentation for Object, Var and Varholder lead me to believe that given the following setup:

std::vector<DynamicStruct> testList;
  Object t1;
  t1.set("name","com.tl");
  t1.set("num1",false);
  Object j;
  j.set("testval",testList);

The following call would let me extract the values (similar to my other use of Object with primitives and basic strings)

` auto retB

I've wanted to craft a "1 minute", "5 minute", "15 minute" moving average (like a unix load average), but don't know the right r to pass to ewma-timeless to get it.

Either documenting a rule of thumb or providing a mechanism to recreate that would be helpful.

Given the following valid kube config section used to connect to an EKS cluster:

users:
- name: xxx
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - token
      - -i
      - xxx
      command: aws-iam-authenticator
      env:
      - name: AWS_PROFILE
        value: foo

Stern or its dependencies are not switching the `AWS_PRO

Hi there! I wanted to propose adding the following badge to the README to indicate how many TODO comments are in this codebase:

The badge links to tickgit.com which is a free service that indexes and displays TODO comments in public github repos. It

log.debug("A tagged log message", userInfo: Dev.dave | Tag.sensitive)

That's somehow will confuse the user who only advantages one kind of Tag.
Then I suggest appending one demo code as below for that scenario.
log.debug("A tagged log message", userInfo: Tag.sensitive.dictionary)

• Instead of holding implementations for each logging, tracing, metrics providers, establish interfaces.
• Be clear about it in docs
• Store implementations in... nested go modules? Separate project? To agree.

Someone should map publicly available EVTX samples to Sigma rules. This would enable us to automatically test the correctness of generated queries.

Known security-related EVTX repositories:

• https://github.com/sbousseaden/EVTX-ATTACK-SAMPLES
• https://github.com/Cyb3rWard0g/mordor

Feel free to extend the list.

Mapping should be:

Sigma rule -> Repository/EVTX ( -> expected matched

const char* getIp(void) {
return "192.168.1.1";
}

above should be

const char* getIp(const el::LogMessage *l) {
return "192.168.1.1";
}

I don't want to generally enable the tracker but need activate it by middleware or command.

The "use_middleware" seems not to be implemented.

How to start it?
use Tracker;
Tracker::currentSession();

Doesn't work!!

It only works with 'enabled' => true, in the config for each request.

Bug Report

The [STREAM_TASK] configuration block was documented for v1.3, but I'm unable to find documentation for this in the v1.4 docs.