Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Flink logging receiver #632

Merged
merged 17 commits into from
Jun 18, 2022
Merged

Add Flink logging receiver #632

merged 17 commits into from
Jun 18, 2022

Conversation

JonathanWamsley
Copy link
Contributor

Example output

{
  "insertId": "148gda2f1jvvvu",
  "jsonPayload": {
    "source": "org.apache.flink.runtime.entrypoint.ClusterEntrypoint",
    "message": "        [] -  Starting StandaloneSessionClusterEntrypoint (Version: 1.14.4, Scala: 2.11, Rev:895c609, Date:2022-02-25T11:57:14+01:00)"
  },
  "resource": {
    "type": "gce_instance",
    "labels": {
      "instance_id": "8710493455276707297",
      "project_id": "otel-agent-dev",
      "zone": "us-central1-a"
    }
  },
  "timestamp": "2022-05-26T17:12:02.616Z",
  "severity": "INFO",
  "labels": {
    "compute.googleapis.com/resource_name": "flink-debian2"
  },
  "logName": "projects/otel-agent-dev/logs/flink",
  "receiveTimestamp": "2022-05-26T17:12:22.426334126Z"
}

@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 26, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 26, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 31, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 31, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 31, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 31, 2022
@JonathanWamsley
Copy link
Contributor Author

@ridwanmsharif sles 12 does not appear to be building correctly. When I try to build the sles12 docker target locally or test with kokoro I get an error

#5 29.18 Problem: systemd-devel-228-27.2.x86_64 requires libsystemd0 = 228-27.2, but this requirement cannot be provided
#5 29.18   uninstallable providers: libsystemd0-228-27.2.x86_64[OSS]
#5 29.18  Solution 1: downgrade of libsystemd0-228-71.1.x86_64 to libsystemd0-228-27.2.x86_64
#5 29.18  Solution 2: do not install systemd-devel-228-27.2.x86_64
#5 29.18  Solution 3: break systemd-devel-228-27.2.x86_64 by ignoring some of its dependencies
#5 29.18 
#5 29.18 Choose from above solutions by number or cancel [1/2/3/c] (c): c
#5 ERROR: executor failed running [/bin/sh -c set -x; zypper -n install git systemd autoconf automake flex libtool libcurl-devel libopenssl-devel libyajl-devel gcc gcc-c++ zlib-devel rpm-build expect cmake systemd-devel systemd-rpm-macros &&     mv /var/lib/ca-certificates/pem/DST_Root_CA_X3.pem /etc/pki/trust/blacklist/ &&     update-ca-certificates &&     zypper addrepo https://download.opensuse.org/repositories/home:Ledest:devel/openSUSE_Leap_42.3/home:Ledest:devel.repo &&     zypper -n --gpg-auto-import-keys refresh &&     zypper -n update &&     zypper -n install bison>3.4 &&     ln -fs /usr/lib/systemd /lib/systemd]: exit code: 4
------
 > [sles12-build 2/9] RUN set -x; zypper -n install git systemd autoconf automake flex libtool libcurl-devel libopenssl-devel libyajl-devel gcc gcc-c++ zlib-devel rpm-build expect cmake systemd-devel systemd-rpm-macros &&     mv /var/lib/ca-certificates/pem/DST_Root_CA_X3.pem /etc/pki/trust/blacklist/ &&     update-ca-certificates &&     zypper addrepo https://download.opensuse.org/repositories/home:Ledest:devel/openSUSE_Leap_42.3/home:Ledest:devel.repo &&     zypper -n --gpg-auto-import-keys refresh &&     zypper -n update &&     zypper -n install bison>3.4 &&     ln -fs /usr/lib/systemd /lib/systemd:
------
executor failed running [/bin/sh -c set -x; zypper -n install git systemd autoconf automake flex libtool libcurl-devel libopenssl-devel libyajl-devel gcc gcc-c++ zlib-devel rpm-build expect cmake systemd-devel systemd-rpm-macros &&     mv /var/lib/ca-certificates/pem/DST_Root_CA_X3.pem /etc/pki/trust/blacklist/ &&     update-ca-certificates &&     zypper addrepo https://download.opensuse.org/repositories/home:Ledest:devel/openSUSE_Leap_42.3/home:Ledest:devel.repo &&     zypper -n --gpg-auto-import-keys refresh &&     zypper -n update &&     zypper -n install bison>3.4 &&     ln -fs /usr/lib/systemd /lib/systemd]: exit code: 4

@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 6, 2022
@JonathanWamsley JonathanWamsley marked this pull request as ready for review June 7, 2022 13:21
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 7, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 7, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 8, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 8, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 9, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 9, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 14, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed kokoro:force-run Forces kokoro to run integration tests on a CL labels Jun 14, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 14, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 14, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 14, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 14, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 16, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 16, 2022
@ridwanmsharif ridwanmsharif merged commit bc1e111 into GoogleCloudPlatform:master Jun 18, 2022
@@ -0,0 +1,36 @@
public_url: "https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/third-party/flink"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't be set as this is a 404 non existent link.

When google technical writer has the documentation, we will set this public_url in post agent release jobs :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh great catch! Will fix this as part of the flink metrics PR. Also made a pass through the other PRs that added this and commented on them too.

This was referenced Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants