Skip to main content

Library for building InfraSonar probes

Project description

CI Release Version

Python library for building InfraSonar Probes

This library is created for building InfraSonar probes.

Environment variable

Variable Default Description
AGENTCORE_HOST 127.0.0.1 Hostname or Ip address of the AgentCore.
AGENTCORE_PORT 8750 AgentCore port to connect to.
ENCRYPTION_KEY default Use your own encryption key for encrypting secrets in the YAML file.
INFRASONAR_CONF /data/config/infrasonar.yaml File with probe and asset configuration like credentials.
MAX_PACKAGE_SIZE 500 Maximum package size in kilobytes (1..2000).
MAX_CHECK_TIMEOUT 300 Check time-out is 80% of the interval time with MAX_CHECK_TIMEOUT in seconds as absolute maximum.
DRY_RUN none Do not run demonized, just return checks and assets specified in the given yaml (see the Dry run section below).
LOG_LEVEL warning Log level (debug, info, warning, error or critical).
LOG_COLORIZED 0 Log using colors (0=disabled, 1=enabled).
LOG_FTM %y%m%d %H:%M:%S Log format prefix.
OUTPUT_TYPE JSON Set the output type to JSON or PPRINT (Only for a dry run).

Usage

Building an InfraSonar.get_state

import logging
from libprobe import logger
from libprobe.asset import Asset
from libprobe.probe import Probe
from libprobe.check import Check
from libprobe.severity import Severity
from libprobe.exceptions import (
    CheckException,
    IgnoreResultException,
    IgnoreCheckException,
    IncompleteResultException,
    NoCountException,
)

__version__ = "0.1.0"


class MyFirstCheck(Check):

    key = 'myFirstCheck'
    unchanged_eol = 0  # Can be for example 14400, to prevent sending the same
                       # check result for the next 4 hours (0=disabled)

    @staticmethod
    async def run(asset: Asset, local_config: dict, config: dict) -> dict:
        """My first check.
        Arguments:
        asset:
            Asset contains an id, name and check which should be used
            for logging;
        local_config:
            local configuration for this asset, for example
            credentials;
        config:
            configuration for this check; contains for example the
            interval at which the check is running and an address of
            the asset to probe;
        """
        if "ignore_this_check_iteration":
            # nothing will be send to InfraSonar for this check iteration;
            raise IgnoreResultException()

        if "no_longer_try_this_check":
            # nothing will be send to InfraSonar for this check iteration and
            # the check will not start again until the probe restarts or
            # configuration has been changed;
            raise IgnoreCheckException()

        if "something_has_happened":
            # send a check error to InfraSonar because something has happened
            # which prevents us from building a check result; The default
            # severity for a CheckException is MEDIUM but this can be
            # overwritten;
            raise CheckException("something went wrong", severity=Severity.LOW)

        if "something_unexpected_has_happened":
            # exceptions will be converted to CheckException, MEDIUM severity
            raise Exception("something went wrong")

        # A check result may have multiple types, items, and/or metrics
        result = {"myType": [{"name": "my item"}]}

        if "result_is_incomplete":
            # optionally, IncompleteResultException with severity;
            # the default severity is LOW.
            raise IncompleteResultException('missing type x', result)

        if "not_count_as_check_result":
            # optionally, NoCountException can be raised in which case the
            # check result is not counted by InfraSonar; Thus, the last seen
            # services will not "see" this check result.
            # A severity can be given if we also want a check error;
            # (similar to the IncompleteResultException exception)
            raise NoCountException('do not count this check result', result)

        # Use the asset in logging; includes asset info and the check key
        logging.info(f"log something; {asset}")

        # In alpha versions and debug logging enabled, unknown exception will
        # be logged when debug logging is enabled.
        # You may use logger.exception() yourself if you want exception
        # logging for debug logging only.
        try:
            42 / 0  # ZeroDivision error for example
        except Exception:
            logger.exception()  # log the exception only when DEBUG logging

        # Return the check result
        return result


if __name__ == "__main__":
    checks = (
        MyFirstCheck
    )

    # Initialize the probe with a name, version and checks
    probe = Probe("myProbe", __version__, checks)

    # Start the probe
    probe.start()

On CLose

Using the set_on_close() method, it is possible to configure a method which will be called before the probe is stopped. This can be useful in case you want to nicely close some connections.

async def custom_on_close():
    ...

probe = Probe("myProbe", '3.0.0', {})
probe.set_on_close(custom_on_close)

ASCII item names

InfraSonar requires each item to have a unique name property. The value for name must be a string with ASCII compatible character. When your name is not guaranteed to be ASCII compatible, the following code replaces the incompatible characters with question marks (?):

name = name.encode('ascii', errors='replace').decode()

Config

When using a password or secret within a config section, the library will encrypt the value so it will be unreadable by users. This must not be regarded as true encryption as the encryption key is publicly available.

Example yaml configuration:

exampleProbe:
  config:
    username: alice
    password: secret_password
  assets:
  - id: 123
    config:
      username: bob
      password: "my secret"
  - id: [456, 789]
    config:
      username: charlie
      password: "my other secret"
otherProbe:
  use: exampleProbe  # use the exampleProbe config for this probe

Dry run

Create a yaml file, for example (test.yaml):

asset:
  name: "foo.local"
  check: "system"
  config:
    address: "192.168.1.2"

Run the probe with the DRY_RUN environment variable set the the yaml file above.

DRY_RUN=test.yaml python main.py

Note: Optionally an asset id might be given which can by used to find asset configuration in the local asset configuration file. Asset config is also optional.

Dump to JSON

A dry run writes all log to stderr and only the JSON dump is written to stdout. Therefore, writing the output to JSON is easy:

DRY_RUN=test.yaml python main.py > dump.json

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

libprobe-2.0.5.tar.gz (31.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

libprobe-2.0.5-py3-none-any.whl (31.7 kB view details)

Uploaded Python 3

File details

Details for the file libprobe-2.0.5.tar.gz.

File metadata

  • Download URL: libprobe-2.0.5.tar.gz
  • Upload date:
  • Size: 31.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.3

File hashes

Hashes for libprobe-2.0.5.tar.gz
Algorithm Hash digest
SHA256 312364c17578fb4ea40d291efa7f597ad9f04579e3c1987a9eeaf7b93415d5e6
MD5 acc3d745abcf150065858029bead2451
BLAKE2b-256 b24b2ec145b2d746ce6130f1048cc2adf0cd122e9e6576e2b136a72936179824

See more details on using hashes here.

File details

Details for the file libprobe-2.0.5-py3-none-any.whl.

File metadata

  • Download URL: libprobe-2.0.5-py3-none-any.whl
  • Upload date:
  • Size: 31.7 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.3

File hashes

Hashes for libprobe-2.0.5-py3-none-any.whl
Algorithm Hash digest
SHA256 3bbfe01f6dfde4f1c6d436fc6b022825dbae83ae17943aa91eb5d1f8928803f4
MD5 80070027fe427be450e542f7c07c72cd
BLAKE2b-256 60d52d10d5a1af451516bd92d1a9d43265792ab185458bddf89cd3b2735ebd37

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page