feat: add "not equal" support to the query filter

[qingling128]

Fixes #10

Added unit tests.

[qingling128]

Rebased off the latest master. Can someone help take a look at this one. Should be fairly straight forward.

[qingling128]

Can someone help with this PR?

[busunkim96]

@qingling128 Apologies, I didn't see this until now.

Is there a way to do the filter by using the generated code directly? https://github.com/googleapis/python-monitoring/tree/e4bc5682d39f7e5938868497496f5d49318cee43/google/cloud/monitoring_v3/proto

It looks like this client was originally handwritten and query.py is a remnant of that. I believe it should be possible to use the generated library exclusively at this point though.

[qingling128]

Hi @busunkim96 ,

We are currently trying to use the library in the following way:

from google.cloud.monitoring_v3 import query as query_v3

    query = query_v3.Query(
        self._client,
        self._project_id,
        metric_type,
        end_time=end_time,
        minutes=look_back_minutes)
    query = query.select_resources(
        resource_type=resource_type, **resource_labels)
    query = query.select_metrics(**metric_labels)
    query = query.align(metric_aligner, minutes=metric_alignment_minutes)
    query = query.reduce(metric_reducer)

Could you elaborate a bit on the suggestion to do the filter by using the generated code directly? I'm not very familiar with what the best practice is for the usage of this library. I found some documentation here: https://cloud.google.com/monitoring/docs/reference/libraries#client-libraries-usage-python. But it does not mention how to query time series though. The code above was put together after reading the source code for a bit.

[qingling128]

@busunkim96
Gentle ping.

[qingling128]

Added the documentation link as suggested and rebased from upstream master.

[gcf-merge-on-green]

Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR

[gcf-merge-on-green]

Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, or one of your required reviews was not approved. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[qingling128]

@busunkim96 - Any chance you know why Kokoro is stuck in the Waiting for status to be reported state?

[busunkim96]

@qingling128 Kokoro doesn't run automatically for people who do not belong to the GitHub 'googleapis' org.

[qingling128]

@busunkim96 - Thanks for the help to trigger the Kokoro test. The test seems to be failing for a bunch of documentation format check failures that predates this PR. Any suggestion for what I should do with them?

https://source.cloud.google.com/results/invocations/fd68debc-462a-4dd6-b8f3-71c59cf5c1e8/log

[busunkim96]

Ah, you can ignore the Kokoro docs-presubmit check. It's a new job whose configs haven't trickled through yet. It looks like the only outstanding issue on the main Kokoro build is lint. I just pushed to your branch, so hopefully it passes. 🤞 Thank you for your patience!

[qingling128]

@busunkim96 - Thanks! Kokoro build passed. The docs-presubmit still blocks merging though. How can we skip that check?

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, or one of your required reviews was not approved. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[qingling128]

@busunkim96 - Can we force submit this one and bypass the docs-presubmit failure?

[qingling128]

Thanks!

[qingling128]

BTW, do we have any scheduled release coming?

[busunkim96]

@qingling128 I merged the release PR so it should be out to PyPI in the next 15 or so minutes. #48

[qingling128]

Wow. That's so fast. Thank you so much!