nasa / nasa/cFS

use appid with perfid for apps

Open
#8 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C
Stars
1.5k
Forks
391
Avg merge
1d 11h
Merged PRs (30d)
19

Description

Is your feature request related to a problem? Please describe.
Currently apps define their perfid when using the performance logging framework, but there's no mechanism currently to ensure that the perfid is unique to that application and could result in confused perf logs.

Describe the solution you'd like
One option would be to use the appid generated when the application is registered (but will need to be reported somehow so that a performance analysis tool can crosswalk from runtime-generated perfid's to the applications.)

Describe alternatives you've considered
Three alternatives: 1) a separate perfid registry/table in memory, 2) some sort of compile-time tool to generate ID's, 3) a textual identifier (that can be "namespaced".)

Additional context
Discussed at CCB 2019-09-04

Requester Info
Chris Knight, Christopher.D.Knight@nasa.gov, NASA Ames Research Center

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name implementation files, tests, or entry points. Start by locating the performance logging framework and application-registration code, then determine how runtime perfid values are generated and reported. Done should include a decided uniqueness mechanism and a way for analysis tools to crosswalk perfids to applications.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.